Milamber

Nice! A Enterprising new Feature!

Hercules Ultimate Localization Design
Hello~! - What?!
Servers are now able to run under any number of languages, without having any of the default files modified Designed by Haruna and Ind  
Translating NPCs without editing them
By launching map server with the --generate-translations param a .pot (.po template) file will be created with all of the servers translate-able strings (including all npc dialogue), this file can be edited in text mode or by utilising any .po editor (there are many out there; for a high range of OSes) A .po file does not need to be fully translated to be used, map server will know when loading the file, and will fallback to the hardcoded string in the npc files as necessary Users are able to change their language with the new @lang command, @lang controls what language users see in @commands (msg_txt stuff) as well as over npc dialogues map-server.conf has a new setting called default_language where server owners may specify which language should be used as a base When you have a new .po file you want map server to use, add it to db/translations.conf Easy to Maintain
Since .po is a widely used format there are many tools that can help with merging for example Poedit, which easily consolidates a translated .po file with a newly generated .pot. For example when you have a translated .po and since it was created npc dialogs were added or modified all you have to do is launch map server to generate a new .pot, open your old .po in Poedit, go "Catalog -> Update from POT file" and it will insert the new translatable strings without touching your existing translations, it will also notify you of any "obsolete" strings that are in your .po file but that are no longer in use Script Command Macro
Besides messages.conf, all the dialogue utilised by 'mes' and 'select' is included in the .pot automatically, this patch also introduces a mechanism for utilising strings outside of these commands, the script macro _() which can be employed just as if it were a script function, for example set .@status$,_("Available"); tells map server to export "Available" as a translate-able string when it is run with --generate-translations (when running map server normally the macro has no overhead during runtime) Special Thanks to
Raizen and Roberto from Cronus, we would not have worked on this if it weren't for them Links~!
Commit Editing Example

^ I think harmony only supports up to 2012-04-10..

Thanks a lot for continues updating this harmony patch @ @ossi0110 !

i know that 2012-04-10ragexe was one of them 

Wow awesome thanks osso010 wha client or diff version supported on this patch? thanks and godbless

If you want it just to be added into your server, it's quite easy.
 
Just open your src/map/map.h and look for all the race declarations. They are on an enum like this on line 257:
enum { RC_FORMLESS=0, RC_UNDEAD, RC_BRUTE, RC_PLANT, RC_INSECT, RC_FISH, RC_DEMON, RC_DEMIHUMAN, RC_ANGEL, RC_DRAGON, RC_BOSS, RC_NONBOSS, RC_NONDEMIHUMAN, RC_MAX};  
Just add your entry there wherever you want, before RC_MAX. It's common practice to add it after the last race that has been declared (RC_NONDEMIHUMAN) but it's up to you. Keep in mind this enum assigns consecutive number identifiers for each item on it. You may also want to add your new race to the scripting constants so that you can use it in scripting in db/const.txt (look again for the race definitions and follow the structure, but they aren't on an enum this time).
 
 
You could also want to edit some atcommands or script commands to adapt them to the new race (especially @mi). Any special feature you want for the race other than existing and being applied to mobs and whatever other non general feature must be added by you.