Ai4rei

Applied the fix I was talking about, both successfully tested on 2012-07-02aRagexeRE. Please try again.

Are you sure, that the head palette diff works? I have found an another issue with the diff, but that bug would affect the head palettes as well.

Still crashing on palette 1 or something else?

Done. As in? Rigging in the command line or an entire login window? Don't know what's different, there was no WDGSkipPacketHeaderObfuscation in r25.

While I'd very appreciate support of my food-supply, I'm not quite sure how much against the rules it is here, since I'm not a rA dev, and I don't want to make money of someone else's work either. SF somehow lost the file update, the file in the download area was still the old one. For now it's deleted. I'll wait for the mirrors to reflect this change and then re-upload it again in a hour or two. Edit: Updated, also fixed some 2010 and 2011 clients not getting any match for both head and body palettes.

Done. The diff removes two arguments from a function call, but I forgot to adjust the stack clean up >__>'... Fixed.

Added WDGRemoveHourlyGameGrade WDGRemoveQuakeSkillEffect WDGSharedBodyPalettes Updated WDGEnableAuraOverLvl99 WDGOnlyFirstLoginBackground WDGOnlySecondLoginBackground WDGTranslateClientIntoEnglish binary builds, sources Kratos: It is visible even when instant casting.

That should be possible to do server-side.

I don't mind as long as there is sufficient feedback when it does not work, since I do not have time to actually test it on various clients; I only test whether the hex in itself is applied correctly.

EvilPuncker: Updated WDGTranslateClientIntoEnglish, decided to call it "Make Character", though (interface and source calls it that way). Expect shared palettes this weekend, unless somethings screws up my free-time. WDGRemoveQuakeSkillEffect and WDGRemoveHourlyGameGrade are in testing. Remaining stuff should be done within next days. Judas: There is a WDGDisableMultipleWindows already.

Added WDGEnableAsciiInText and WDGRemoveHourlyPlaytimeMinder (binary builds, sources). Also before someone asks, I won't do anything to unpack themida clients (time consuming), but... I see a chance for hot-patching becoming the next "diffing" method.

In an attempt to recover the lost changes to get the source to the state of the last binary release, I'd like to ask you (when you have the time) if you happen to have an, at least approximate, list of the changes missing.

So far I'm reading into the SDK and related code to get how it works. Enable ASCII characters will come, too.

Then let me pull some assumptions out of my sleeve, correct me if I'm wrong. Shared Palettes Makes the client use the same clothes palette set (ex. body_<id>.pal) for all classes instead of having to make a palette set for each class (<class>_<gender>_<id>.pal). Disable (Multiple) Windows Preventing the client from being started multiple times simultaneously.

I wonder why I haven't noticed this earlier. Then if there is still interest from the community, I would resume the development as part of the atwl project, of course while keeping the attribution intact. Kind of reminds me of my HDD crash, were I was about to lose sources of all projects, and I don't want this project to die either.

It does not match for most recent clients, that's why I wrote, that I need a client version, if it does not work for someone.

Squishyyy: Whether your OS is 32-bit or 64-bit does not matter, as long Gravity does not release a 64-bit version of the RO client. MuzTank: Do not change the OptionInfo.lub in \RO\System . Also the registry part (yes the Lua setup still saves few settings in the registry) needs Admin rights, which the setup should ask for. Actually, you should not even be able to run the setup without administrator rights.

Hmm... I have written a hex before for this. If it does not work for you, you will have to tell your client version (XXXX-XX-XXyRagexeRE).

crypt.cpp looks pretty familiar, so I don't think you should attribute it to yourself when you did not write it, but only modified it a little.

Have tested the most recent version with a clean 2012-04-10aRagexeRE and it starts without warnings, with specified resolution (ex. 800x600). Taking the second error message into account, you are probably missing option defaults lub file, or rather the entire system folder in your RO folder. Following files should be in there: \RO\System\MsgString.lub \RO\System\OptionInfo.lub (read-only setup defaults + OptionInfoList and CmdOnOffList declaration) \RO\System\Towninfo.lub (2nd error message) \RO\System\itemInfo.lub \RO\System\Font \RO\System\Font\RixSquirrel_12.eot \RO\System\Font\RixMiniHeart_10.eot \RO\System\Font\RixNHCgogo_10.eot \RO\System\Font\RixSquirrel_10.eot \RO\System\Font\RixMagic_10.eot \RO\System\Font\RixLoveangel_10.eot \RO\System\Font\RixLoveangel_12.eot \RO\System\Font\RixJJangu_10.eot \RO\System\Font\RixKid_10.eot \RO\System\Font\RixFreshman_10.eot \RO\System\Font\NHCgogo_10.eot \RO\System\Font\NHCgogo_12.eot \RO\System\Font\RixDiary_10.eot \RO\System\LuaFiles514 \RO\System\LuaFiles514\OptionInfo.lub Override settings (OptionInfo.lua) saved by Setup and Client are in SaveData folder. Because the official setup does this as well to keep settings written by the client.

Hmm... both should be equivalent Lua code, can you tell me any error messages the client is printing? The latest version has been thoroughly tested with 2012-07-02aRagexeRE. The source is not up-to-date and does not support Lua clients, you might want to tell me the errors you got while compiling though.

Released v2.4.0, resolves issues with Lua settings not being used by the client, among others. Updating is highly recommended.

It's not open as in open-source, but open as in free. That does not prevent me from releasing the source on some occasions, though.

There's a bug in OpenSetup, which causes the client, among others, ignore the window size settings. Fix is in progress.

Released v2.3.0, with Czech and Korean translations; no functional changes.