Gepard

@bgamez23 You probably need to look into addons/content_management/themes/, copy default and rename it to emphaino. @JulioCF You forgot to uncomment the 2 lines that define top-level menu 'Main Menu' (the one that will have forums link in it).

Well then, if pros and cons have to be studied, then go study first, and only then come here and share your wisdom. Cause right now you're talking some totally general stuff about how cool would it be to do this and that, but you are not willing to discuss any specific issues related to FluxCP, which this topic happens to be about. I'm not discrediting anything you say, I'm just pointing that what you're saying isn't really useful for further FluxCP development, so in fact irreleveant. I don't see the point in discussing "why FluxCP isn't so awesome as I'd like it to be" or similarly abstract stuff, but unfortunately that's exactly what you're trying to "discuss" here. It's you who started the bashing without giving any reasonable points and it's you who first came to weird conclusions ("this topic is fluxcp ad"). If you claim that some app has "conception fails and critical exploits" you must have something to back up your words. That's what I expect from a serious discussion. That being said, I'm waiting for a PM with details about the exploit you mentioned. Last but not least, I'm sorry for being so straightforward. This is just how I am, and I'm not really hostile towards you or anything like that.

Not every new technology or design pattern is worth following or being used. Software doesn't need to be state-of-the-art to be a good piece of software. You seem to be focused too much on internal aspects of the control panel, and forgetting that first and foremost it is a tool, an utility. It has to work and work properly most of the time - that is what is expected from a program. Then, it should be easy to maintain and develop. (BTW, using latest technologies is great way to create a steep learning curve for anyone who'd like to contribute to the project, so it can have exactly opposite effect) And only then it should be beautiful (code-wise, internal design-wise, not talking about appearance here). If you have too much free time nobody is holding you from using all kind of latest technology and writing your own state-of-the-art control panel for ragnarok server. Also, if you realized there are some real exploits in current code of FluxCP, you should just fix it or at least report it, instead of complaining. Otherwise, I can't take what you're saying seriously. I respect you having great deal of knowledge about webcoding, but sometimes you need get off your high horse and help less experienced people or you just start to sound like a prick. Now I have the feeling that it's you advertising yourself in this topic, trying to make an impression how good you are at things, and how cool would be the control panel you could write. Please refrain from it, showcase/bragging topics belong to other sections. Once again, point to any bug/exploit in current fluxcp, or at least justify using any of the stuff you mention with real use-case examples, instead of making general remarks about webcoding. All input is appreciated, but it has to be more specific. "FluxCP is not using latest technologies" is NOT a useful suggestion. Useful one would be: in file foo.php, we could use new feature from foolib ver. 1234 so that we can simplify the code in file bar.php and make it easier to create new foobars for baz module.

If we followed that logic, the very first piece of software that should be thrown into the trash bin and rewritten from scratch is athena/hercules. FluxCP has actually a well structured and documented code, quite easy to understand, follow and maintain. Did you even take a look at its source? You're talking about using latest technologies.... which one do you exactly think could be used in a new, better control panel, that isn't present in flux? Just asking, cause all your arguments are valid but you haven't show us yet how they apply to fluxcp.

I don't really see problems with piece of software being few years old. If there are issues with it, they can be fixed, code can be improved etc. Writing new application from scratch doesn't guarantee it would be better. More likely there will be some new bugs in it, and it will take time to find and fix them all. FluxCP is matured enough, and as far as I know, there haven't been any major problems with it, despite it being used in hundreds of servers.

In each of your addon's folder there is `themes` folder which contains views for all themes. Just make a copy of `default` folder and rename it to `emphaino`. You should be able to use your addons with new theme then. If it doesn't look good you'll have to make some edits (but it should be good enough).

In fact, Hercules is moving to store passwords hashed with bcrypt. You can see progress on this feature here: https://github.com/HerculesWS/Hercules/issues/74 and here: https://github.com/HerculesWS/Hercules/compare/bcrypt

`item_db2` table has the same name in pre-RE and RE setups, but different layout. If your Hercules server is using pre-RE configuration, you need to import `item_db.sql` and `item_db2.sql` from `sql-files`. If it's Renewal server, import `item_db_re.sql` and `item_db2_re.sql`. If you modified `config/servers.php` and changed from 'Renewal' => true to false, you need to re-import `item_db2.sql` script, so table `item_db2` has the pre-RE layout. Currently it's impossible to have both pre-RE and RE item tables in the same database.

It's already been fixed. Thank you for your report. The only pre-existing theme that was supplied with previous versions of FluxCP was 'default' theme. And it of course is also included in Hercules FluxCP and works as usual. If you want to use a custom-made theme, it should work without major problems. Compared to most recent revision of fluxcp-ra, the only updated module is item database, so you might need to make appropriate changes in this part of your theme. Other than that, it will be also missing theme selector (only relevant if you want to use other themes as well). You can copy appropriate snippets of code from default theme. I will also post detailed explanation how to do this soon. If you have any custom modules (like for example, additional ranking) and want to make them available with new emphaino theme, they should work without problems as well, since most pages are 99% identical with default theme, it's all css magic. So just copy missing views into themes/emphaino (or addons/youraddon/themes/emphaino) and they should become visible in new theme as well.

Flux Control Panel for Hercules Flux CP is now officialy available for Hercules! It is fully working with both pre-Renewal and Renewal Hercules servers. We will continue developing it, so it is always up-to-date and compatible with latest Hercules. New theme Hercules' Flux CP comes with a brand new theme. It's a grey-ish modern and clean HTML5 theme, called Emphaino. It has a nice dropdown menu located on top of the screen, and a customizable footer area, where you can put some stuff that should be visible all the time (like links to social media, forums etc.). A picture is worth a thousand words: It's a HTML5 theme, so it requires a decent browser, or IE9+ (if you insist on using that). Theme selection Having two themes is great, but until now it was impossible to make use of them both. That's why theme selector has been added to both themes, so your users can pick whichever theme they like more. Again, preview: Extra credits Authors of original FluxCP & FluxCP-rA. Authors of Emphaino theme (originally for Wordpress). Download Hercules' FluxCP Github repository: https://github.com/HerculesWS/FluxCP Issues Bug reports, questions and suggestions are all welcome directly on GitHub: https://github.com/HerculesWS/FluxCP/issues Enjoy~

Increase MAX_MOB_DB. Or lower ID of your custom monster.

//this is the item choicessetarray .@beadID[1],4739,4709,4749,4729,4759,4719,4790,4794,4763,4799,4802,4825,4831,4841,4844,4849,4848,4852,4868;for( set .@n,1; .@n <= 3; set .@n, .@n+1 ) {set .@BeadMenu$,"";//loop for menufor( set .@i,1; .@i < getarraysize( .@beadID ); set .@i,.@i + 1 ){ if ( .@beadID[.@i] != 0 ) { set .@BeadMenu$,.@BeadMenu$ + getitemname( .@beadID[.@i] )+":"; } else { set .@BeadMenu$,.@BeadMenu$ + ":"; }}//makes a selection of what item you wantset .@s, select( .@BeadMenu$ );set .@BeadChoices[.@n], .@beadID[.@s];set .@beadID[.@s], 0;}

Currently there is no stable branch. If you're not satisfied with stablility of recent revisions, consider using slightly older checkout of Hercules.

Suggestion: Make the command return opaqueness level of the emblem, for example if 30% of pixels in the image is magenta (transparent), return 70 (70% is opaque). If it's all transparent return 0, and also return 0 if there is no emblem. This way you can set your own threshold in scripts, and allow some transparency.

That's exactly my point. You want to make @reloadnpc save some part of what it reloads, because you don't want it to reload everything, but there's no other way. The correct solution in such case is to provide extra commands to unload just right things. As for things you mentioned, you can refresh a custom function just by loading an updated version of it with @loadnpc. You can also call OnInit label from another temporarily loaded script. Or you can use an NPC tthat would take your input (via inputbox) and call that event, like this one: // NPC to trigger other NPC events manually// To "click" this NPC, whisper to NPC::donpcevent as you would// to any other player.- script donpcevent -1,{ end;OnWhisperGlobal: if (getgmlevel() >= 99) { while (1) { mes "Please enter eventname in"; mes "^0000FFNPCName::Event^000000 format."; mes "Enter ^FF00000^000000 to cancel."; next; input .@event$; if (.@event$ != "" && compare(.@event$, "::")) break; if (.@event$ == "0") close; } mes "Triggered event:"; mes "^0000FF" + .@event$ + "^000000."; donpcevent .@event$; close; } end;}