Hi~
I would like to buy unpacked Salvation client (protocol 140) for Taiwan version, here is the download link to Taiwan client file:
http://tw.ncsoft.com/lineage2/download/index.aspx
Please PM me for price and payment method.
Thanks
You have to unpack THEMIDA from L2.bin (It's actually L2.exe, just protected) and engine.dll and it's not a easy job.
After that you can use patcher to patch L2.exe.
Lineage II DAT files are encrypted by RSA and their key stored in L2.bin, it is still a mystery so Dstuff's utility replaces it with a new RSA key.
If you patch DAT file you must either patch L2.bin (protected by themida) as well or use loaderCT1++ to launch game.
You have to patch all *.dat as well as L2.ini and user.ini (Use L2 Fileedit to open and save it )
That's all.
By the way, NC is using new launcher so you should no longer be able to launch game via loaderCT1++ if you play official server
Here's how I did :
1. Use l2encdec to patch all *.dat and L2.ini/user.ini under system folder.
2. Use L2 FileEdit to edit the file you wish to.
3. Launch game with LoaderCT1++ (If you know how to patch RSA in packed L2.bin then you don't need this step)
4. Login and check if setting is taking effect.
On my machine I have to use LoaderCT1++ with parameter "-n 10" to get it launched flawlessly, I don't know why but it just works fine.
But LoaderCT1 does not work anymore with new NCLauncher for Infinity Odyssey and I'm still looking for new way to launch "patched" Lineage II.
Please try following first:
1. Use L2 Fileedit to open your itemname-e.dat.
2. Don't make any change, just encrypt it back.
If it is encrypted successfully then your DDF is correct and you have to check those changes you want to make; if encryption failed, please share your DAT and DDF to me.
Sorry for late.
Please check this DDF:
http://rgho.st/84bypPtQQ
I can decrypt and encrypt armorgrp.dat you provided to me with this DDF.
This is for Infinity odyssey:Rhapsody.
I checked your DDF which is exactly my previous work on Rhapsody.
Care should be taken while you editing texture column, here is an example:
Where cntm and cntt are counters that define how many UNICODE strings (texture file name) should present.
If you filled wrong value (e.g. 5 UNICODE strings but its counter value is 4 ) you'd see error during encoding.
You can try to modify one thing at a time to find out which step goes wrong.
It looks like that L2disasm cannot handle a counter with value greater than 1024 and makes it impossible to decode PawnAnimdata.dat for Helios.
Pawnanimdata now uses dynamic table to reduce file size but it also causes problem on decoding.
Any one has idea on this?
After two weeks of work I finally successfully decoded Armorgrp.dat.
Unfortunately those texture names are now replaced with numbers and I have no idea how to map these numbers to corresponding textures.
You can download my attachment and rename it to armorgrp.ddf.
One DAT solved, 200 DATs to go
Armorgrp.txt