Ind

.@md_name$ = "Endless Tower";would have to become.@md_name$ = _("Endless Tower");

I'm unable to reproduce your issue now though (I addressed it in a commit yesterday)

Try updating hercules and generating a new .pot file, I think this issue has been fixed

atualizada nao necessariamente resolve o problema, tem que ser o lua que corresponde a versão do seu client (se for velho pode ter coisa faltando; se for novo pode chamar funções que o seu cliente nao suporta, etca).

could you upload the .pot you used so I can try it?

Thank you for all the data, much appreciated.

I failed to figure on my own, does the client display any issues when utilizing a map greater than 512*512? I understand map server poses a restriction (which can be increased) for size purposes, but does the client impose any? knowing this would help me work on a feature for the herc. Thanks

Wooonderful people I expect you to know by now that reports do not go in the forum, they go in the bug tracker. Michieru and I have tested this system prior to release under many settings, I suspect all the issues mentioned so far are environment-related and thus I need the proper venue to pose questions on the setup and such, and I can't do it properly on this topic, so I reiterate, reports should go in the tracker. and no, you should not reply here with links to the bug tracker. Thank you.

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 useScript 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 themLinks~! CommitEditing Example

2014-10-22 Client, Roulette and per-char gender! Made Possible Thanks to Yommy We're only able to provide you with this patch thanks to Yommy, Thank you very much! Roulette During test period it will be disabled by default, to enable you must edit conf/battle/feature.conf // Roulette (Note 1)// Requires: 2014-10-22bRagexe or later// Off by default while test version is out; enable at your own risk -- the mean dev.feature.roulette: off Roulette rewards can be defined in db/roulette_db.conf As we understand the coins are points that you obtain by consuming an item, while such an item is not yet available (will be in a upcoming commit), you can set these values with @set command, they're TmpRouletteBronze,TmpRouletteSilver and TmpRouletteGold -- e.g. @set TmpRouletteBronze 5 Requires PACKETVER 20141022 or higher. Where you can get such client? Here (Again, Thanks to Yommy!) In action: http://herc.ws/board/damocles/ind/screenHercules136.jpg Per-Character Gender Sex is now a character table field, which can be defined as 'M', 'F' or 'U'. 'U' being the default value, meaning undefined, which means the accounts gender takes precedence (upcoming) a script command to change a characters gender Requires PACKETVER 20141022 or higher. Where you can get such client? Here (Again, Thanks to Yommy!) In action: http://herc.ws/board/damocles/ind/screenHercules137.jpg Special Thanks to Yommy ..Yommy ...The all-awesome Yommy~! Thank you again! Ziu for extra roulette information (some yet to be applied) Haruna Link~u! Commit 2014-10-22 client