WeeDiffGen

[Judas]

yeah push them =x

[Ai4rei]

Added:

• WDGRemoveLoginErrorCode

  Simple request: remove those debugging numbers by gravity after any message, Rejected from the server (3) and so on

exp-bar queued

[nanakiwurtz]

TranslateClient with backend - waiting for feedback

Sorry, I didn't understand your previous post, can you give an example?

Well, WDGTranslateClientIntoEnglish could be changed to use a back-end file that contains korean+respective translation strings. That would allow you to add translations without having to deal with the source. Just post the desired file format.

[Ai4rei]

The WDGTranslateClientIntoEnglish could be accompanied by some text file, that contains to-be-translated korean text and respective translations, such as

ÆÄƼ°á¼º
Create Party

ÆÄƼÃÊ´ë
Add to Party

which could be edited freely without having to compile the plugin.

[Judas]

i think just a plain text file (.txt) is fine? Unless there is something better than that

[nanakiwurtz]

Oh okay, I'll gather some untranslated data first, I'll post them on this topic, just to keep track of things that still needs to be translated.

After there's enough data, I'll join them in a single file.

[EvilPuncker]

The WDGTranslateClientIntoEnglish could be accompanied by some text file, that contains to-be-translated korean text and respective translations, such as

ÆÄƼ°á¼º
Create Party

ÆÄƼÃÊ´ë
Add to Party

which could be edited freely without having to compile the plugin.

That is cool already, you can do like that, also would be nice to have the max length that we can use in each string like:

//12

ÆÄƼ°á¼º

Create Party

//12

ÆÄƼÃÊ´ë

Add to Party

[Ai4rei]

The max. length can be calculated for most of the strings with (length + 1) aligned to be multiple of 4 (again without 1 byte for the zero-termination). Some strings may have (depending on placement) more space, though.

For example "asdf" uses 4+1 bytes which is 8 bytes when aligned, minus 1 for zero-termination gives 7 bytes available for the string itself.

Someone might make a front-end for editing that file then, that could restrict the text entered with above rule.

[Vianna]

Why don't you add a new data section to the PE with all the translated strings, so there's no limit to the character count? It'd take longer to patch because you would have to search for all references to the string, but wouldn't it be work the effort?

Or maybe you could use the same functions the client uses to access strings from msgstring_kr.lua, using custom indexes (that would look less hacky)

[EvilPuncker]

The max. length can be calculated for most of the strings with (length + 1) aligned to be multiple of 4 (again without 1 byte for the zero-termination). Some strings may have (depending on placement) more space, though.

For example "asdf" uses 4+1 bytes which is 8 bytes when aligned, minus 1 for zero-termination gives 7 bytes available for the string itself.

Someone might make a front-end for editing that file then, that could restrict the text entered with above rule.

lets keep it simple as a .txt file then, since will be hard to find someone to develop this since lately everyone seems busy

[GreenBox]

I'll can try this later, doesn't seem too dificulty

[Ai4rei]

Why don't you add a new data section to the PE with all the translated strings, so there's no limit to the character count? It'd take longer to patch because you would have to search for all references to the string, but wouldn't it be work the effort?

So far I know WDG plug-ins have no means to add new sections and the default all-purpose section is limited to 4096 (would have to modify WeeDiff), needed by other plug-ins for code. Also finding all references is only easy when you have to deal with direct PUSH, only. String arrays (MOV R32,[R32+R32*4]) for example would need a disassembly of the entire code and could still be missed. I don't think it's worth to implement an entire disassembler for just translating the client (among others also beyond my free time and skills).

Or maybe you could use the same functions the client uses to access strings from msgstring_kr.lua, using custom indexes (that would look less hacky)

Since most of the strings use address references rather than function calls (ex. MsgStr for msgstringtable.txt), inserting a function for each string reference is even more complicated. To get space inside the code, you have to steal some code, at least 5 bytes for a 4 byte JMP. Each string would add about 20~22 bytes of overhead (JMP, PUSH, CALL, optionally ADD ESP,4 depending on the lua function, JMP). In short, even worse than the above.

[kyeme]

Hi Ai4rei can you add "Use Official Clothes Palettes All Langtypes" ? Please~ Thank you!

Edited September 27, 2012 by kyeme

[Limestone]

@Ai4rei, How about the Character Selection back to Log in Screen? is there any possibilities to fix that problem?

[Judas]

^ please answer

[Limestone]

Another one Ai4rei, the disabled aura over 99 and 150.

[Brynner]

Another one Ai4rei, the disabled aura over 99 and 150.

i think he already done that

[Vianna]

Another one Ai4rei, the disabled aura over 99 and 150.

I think he said he wouldn't do that one because rAthena already supports it.

[Limestone]

if rAthena supports it. please teach me how o_O

[Ai4rei]

Hi Ai4rei can you add "Use Official Clothes Palettes All Langtypes" ? Please~ Thank you!

Try WDGAlwaysCallSelectKoreaClientInfo.

@Ai4rei, How about the Character Selection back to Log in Screen? is there any possibilities to fix that problem?

I do not support the login window restore and any stuff associated with it.

Another one Ai4rei, the disabled aura over 99 and 150.

conf/battle/client.conf:

max_lv: 98

And set bit 1 in client_limit_unit_lv if not already set, that should do the trick.

[Judas]

@Ai4rei, How about the Character Selection back to Log in Screen? is there any possibilities to fix that problem?

I do not support the login window restore and any stuff associated with it.

is there a reason?

[nanakiwurtz]

is there a reason?

Maybe Ai4rei has already too much work to do

[Ai4rei]

is there a reason?

For one:

Maybe Ai4rei has already too much work to do

And the other is:

I think ai4rei said that kro removed that login functionality, but we'll wait for his reply

I have obsoleted the 'restore login window' diff in favor of packet 0x825.

This also applies to my own login window restore hex.

[Limestone]

@ai4rei, i try max_lv: 98 but it still shows my aura.

[Vianna]

@ai4rei, i try max_lv: 98 but it still shows my aura.

You must change

// Units types affected by max_lv and aura_lv settings. (Note 3)
// Note: If an unit type, which normally does not show an aura, is
//       set it will obtain an aura when it meets the level requirement.
// Default: 0 (none)
client_limit_unit_lv: 0

to

// Units types affected by max_lv and aura_lv settings. (Note 3)
// Note: If an unit type, which normally does not show an aura, is
//       set it will obtain an aura when it meets the level requirement.
// Default: 0 (none)
client_limit_unit_lv: 1