Neo-Mind

longshen Custom Window Title had a bug well actually bug was in the core. ill be updating it soon. Ill check the client date you have mentioned. Ill need to look into how ForceClientHashPacket is implemented (wew that was a mouthful) looks like there was a bug with replacing dword i have fixed it now. I'll update the repo today with all the updated stuff.

what issue are you facing?

hmm odd i can see it . anyways you can also try downloading from my repository . i have added the link in my post.

N.E.M.O. - Neo Exe Modification Organizer Why another client patcher? well 1) WeeDiffGen - isn't working for 2013 clients + it depends on dlls (not that its a bad thing but i like scripting ) 2) xDiffGen - yes its scripted but we need to depend on xdiff files. so i made a new one based on xDiffGen and here it is. The patches are written in QtScript format. Details of making a patch have already been written in a seperate topic - although now it needs to be updated with more details. I have already converted most of the patches from xDiffGen. Why this name? - well I didn't want it to be called * Gen No offense plus someone keeps calling me Nemo in IRC which gave me the idea Snapshot ----------------- How to use? --------------------- 1) First you need to specify your client file in Input Exe file box. If you browse to select the file name, Output Patched box gets updated with a _patched suffix filename automatically. Ofcourse you can select your own name for the output. 2) Next we need to load both the client and the scripts (patches & addons). so click Load Client button. 3) Select the patches you want . In case you patched once before (for whatever date) they will be saved in your local and you can use the Select Previous button to select them again. Also you can try using the Select Rcomnded button to select all the Recommended patches. 4) So your patches are selected and client is loaded what next but to Apply Patches which will generate the output file. In 2.0 version , NEMO also generates a .secure.txt file containing the MD5, SHA1 and CRC32 values of the output exe file which you can use in various tools. 5) You can use the Save Profile and Load Profile buttons for saving/reloading a set of patches & input values, that you have selected (even if they are not applied) for future use. 6) Whenever you apply patches to a client, NEMO updates the patchlist.log file (along with Inputlist.db) in the folder where NEMO.exe is. This file will contain the list of patches you have applied along with their IDs (do not tamper with either of them). Changes in 2.0: ---------------------- 1) I have made some obvious modifications to the interface (you can definitely see the change in case you have seen v1.0). i) Buttons have come downwards and is no longer strippable (toolbar has been fixed in position) ii) New status Label has been added which shows your currently loaded client date and how many patches are selected. iii) NEMO now has support for Addons - scripts that are meant to retrieve data from the client and do its own thing (not patch the client). All the Extract xDiff patches has been added here already. 1 extra addon will be coming soon once i can fix it. iv) New Filter box has been added which does live search (i.e. filter as you type) for filtering out only the patches u want to see. For e.g. if you type color, it will only show patches that have the string color in either it's name or the description. You can also use regular expression . Also you can sort the columns now v) An upcoming feature - Test Patches. this one you can use for testing a newly added patch for a variety of clients that you select. 2) NEMO is no longer there in SVN. I have shifted it to GitHub . The rar file uploaded has the .git file so you should be able to directly pull to get updates. But just in case I have also provided the repository link below. Remember to pull for updates before using NEMO and let me know if you are facing any bugs or issues or if i have missed out on anything. Enjoy . Repository: https://github.com/MStr3am/NEMO.git Download Link: NEMO zip file

Olrox is definitely gonna like that Poring . it looks good but then again I'm no expert to figure out the intricate details . if thats bad english i welcome it

hmm its the same line count as october no change . anyways whats the use if the latest working client isn't needing that many lines.

just checked it now. its not there even in 2013-08-14 client which is the latest working client . I do see that job id used in 2013-10-02 but i believe that client has unpacking issues since gravity have added some additional protections since 2013-08-28 (dunno if k3dT got around that problem though).

kewl . i dont think kRO has that (because they dont have oktoberfest? ). But i guess it can be hexed in probably.

exec ${EMULATOR}athena-start << this will run the athena-start script but the working directory will still be the same and athena-start looks for the server binaries in the working directory i.e. /home what you should be doing instead is. cd $EMULATOR exec athena-start stop or alternatively add $EMULATOR to the $PATH variable instead of ./

@themon that hex has null bytes inside it will stop at the first 00. Here is the original hex. the original text is 845 characters long (excluding the null byte at the end which cannot be avoided). all of the translated text so far are longer than that (1221 characters long). We need a shortened version

i have updated the info in wiki

im working on a new patcher currently so that we can eliminate the need for seperate xDiff files per client but still be easy to make new patches with script. I'll add these as official patches in that once its done. Please be a little patient

I believe these are the packet keys for 2013-08-07 => 3D807D80 , 5E805580 , 7E241DE0 You can look for "68807D803D688055805E68E01D247E" in ollydbg to find them. Remember to put the client in your RO folder and open it in ollydbg from there only and olly needs admin rights.

Guess we should add this to Translate to English Patch .

@Legendary - you forgot the extension (.exe) @minicasio - You might be using a different langtype. Apply the Use SSO Login Packet diff to your client .

dont VS usually convert old solution files to new ones. in your case i would say try using 2012 solution file

going off topic arent we?

now thats interesting although amon ra is odd one out.

its working for me for the same client (although it crashed after showing the sprite - but i think it was an issue with the sprite i used). You need to edit weapontable.lua 1) In Weapon_IDs table add your entry. for e.g. i added Oriental Sword (last entry was for Wizardy Staff which is 97. so i used 98. this is also the classNum value you need to specify in ItemInfo.lua WEAPONTYPE_Oriental_Sword = 98, 2) Next in WeaponNameTable add your sprite suffix. [Weapon_IDs.WEAPONTYPE_Oriental_Sword] = "_Oriental" 3) Next in Expansion_Weapon_IDs map the custom to a weapon type . mine was a 1-H sword so [Weapon_IDs.WEAPONTYPE_Oriental_Sword] = Weapon_IDs.WPCLASS_WEAPONTYPE_SWORD as for view id in item db it is like what is said in the wiki (0-30); i dont think client even checks that value.

that was made for clients which didnt use iteminfo.lua (since post that i didnt see any hardcoded checking). ill try adding a custom weapon when i get home today.

i believe you need to add the skill id to skillid.lua ; description to skilldescript.lua; remaining info like sp per level etc to skillinfolist.lua ; assign to JOBID.JT_WANDERER in skilltreeview.lua all of the lua files are found in lua files/luafiles514/skillinfoz folder.

i thought weapons didnt have limit for new clients hmm. what all files did you update for getting the weapon.

if thats the login server then its normal to see closed connections since we only connect to it while *logging in*.

this looks intriguing nice commit malu. thanks for ur awesome support as usual Yommy, Beret and kyeme

best way to protect client is to make a proper one from scratch that has it in built like KeiKun said. I believe there are many individuals here who knows about handling the various client files. Why not start up an open source project for a client that doesn't die out.?