Jump to content

[Guide] How to remove DDF from .dat files ! Make L2 File Editors to work by Dev


Recommended Posts

Posted

I believe that this guide was missing from a big l2 development & cheating  forum such as this one what you say ?

 

With this tutorial you are able to remove the defenses NCsoft team adds to their systems and doing so you can decrypt their weapongrp.dat of (GoD Tauti example) since till now there exist only simple GoD File Editors.

 

You will find all the appropriate programms Here & here

 

So, let's start:

 

The first step I open a dat file for example l2itemname.data from h5 and paste everything in excell to haddle it easy then, I make a ddf with full UINT format for example:

 

FS = "\t"; 
HEADER = 1; 
RECCNT = 1; 
MTXCNT_OUT = 1; 
MATCNT_OUT = 1; 
ORD_IGNORE = 0; 

{ 
   UINT TEST[5];
}

 

So I will get full numbers in every where. The first number is a trash value, and you will get problems if u dont avoid it. so you can copy tha value and delete it from script with this.

FS = "\t"; 
HEADER = 1; 
RECCNT = 1; 
MTXCNT_OUT = 1; 
MATCNT_OUT = 1; 
ORD_IGNORE = 0; 

{ 
   UINT id
   UINT TRASH;
      ENBBY = [(id,trash_number)];   

}

 

where trash trash_numberis the number that you got in the first script, now the enbby funtion is like a IF, use the value is id = trash_number, so you will use the trash number just in the begin of the script, and not the the others lines so no tras errors. We are just starting now, the script have a value named RECCNT and it will say how many rows you will check and is really use full whe you find a error to focus in the specific lines from the error. I start with RECCNT = 1 so I will focus in the first line. now I use a older ddf and run the l2disarm, I will get a error for sure . now start the hard part, you can use the Funtion ENBBY to check values in every field the problem is thta you can use it only for integer numbers, if the field have a string lines you will have problems, for exacmple let's say the first lines in h5 is:

 

1 stringcode 3 3 stringcode 0 0 0 0
and in GOD is:
1 3 3 stringcode  stringcode 0 0 0 0 your first code in ddf will be UINT

{
    UINT ID;  //nextline you will check if is string or integer the problems is what values use xD? to test well check your H5 to get possibles numbers I will chosse 3 and use this funtion
    UINT TEST;
    UNICODE LOOKING_A_ERROR[1000];
      ENBBY = [(TEST,3)];
}

 

if I get aa error, that mean the values is 3 and maybe i didnt change I will do this in every filed till I get some ddf without errors in the first lines  if I do it I will go the next line maybe I will pass some lines maybe many of then, if I get a error in ahead I will look that lines in the older h5 dat and look for possibles values to test, yea I know this is so freak but it works some times . some usefull info ENBBY is like a If you can get a OR funtion by use ENNBY in a row I mean :

 


ENBBY = [(TEST,3)];
ENBBY = [(TEST,1)]; is line test = 3 or test = 1 or you can get AND FUNTION Using

ENBBY = [(TEST,3),(TEST,1)]; is like test = 3 and test=1, anothe funtion is SKIPIF = [(1),(3)]

FOR EXAMPLE:
UINT ID;
    SKIPIF = = [(1),(3)];

 

it will sypp that field if the value is 1 or 3.

 

Well thats all I know I hope that I was clear enough to understand.. Any replies bad or good are accepted.

- Another useful guide by unexperienced l2 developer Dev.  ;)

Credits : Dev

 

Cheers

 

Posted

So with this tutorial ,files of our patch can be opened only by us?

add the code tags on code lines,it looks a mess now.

With this tutorial you are able to remove the defenses NCsoft team adds to their systems files and doing so you can decrypt their weapongrp.dat of (GoD Tauti example with a God Tauti File Editor) you actually somehow CREATE your own  God Tauti File Editor since till now there exist only simple GoD File Editors. As about the codes I will re-edit my post thanks for reminding.

 

Posted

With this tutorial you are able to remove the defenses NCsoft team adds to their systems and doing so you can decrypt their weapongrp.dat of (GoD Tauti example) since till now there exist only simple GoD File Editors. As about the codes I will re-edit my post thanks for reminding.

Ahhhh.

Because you said Make l2file edits to work by Dev,i understod by the owner of server,the Dev but you were meaning yourself.llolllolool :P

 

Anyway,good tutorial and kinda pro method,gj.

  • 4 months later...
Posted

This is useless for "mortal users" - they wont understand a single word :) I think that maybe few ppl can use Your guide and it's kinda messy. You have explained only a realy basic infos.

With this guide testing each values will take AGES so after all it wont work so good as a guide for random users. You have explained only 2 values as a example but there are many many more problems which ppl wont handle...

But thats only my opinion. But good try i guess.

  • 1 month later...
  • 1 month later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Posts

    • "CAN YOU DO A BULGARIAN REVOLUT?" – WE DID. FIRST DRAFT, NO EDITS The request came in short: a photo of a bank card, Bulgaria, Revolut. We said yes and asked the only question that matters – what data. The client was on the road, asked for a couple of hours, then sent the lot: number, expiry, CVV, payment system, bank, cardholder name. Then came the part the client never sees: - ran the number through Luhn – the check digit has to add up, otherwise the card is dead the second anything automated looks at it - matched the BIN to the issuer: Revolut in Bulgaria isn't a "local bank", the cards run through Revolut Bank UAB. The number range has to actually belong there, not just start with the right digit - built the current design, not a five-year-old picture: vertical layout, flat laser print instead of embossing, correct chip module, contactless mark where it belongs - the payment system logo – with the right gradient where the circles overlap and the wordmark sitting exactly where it should. A small thing that kills half the fakes out there - and finally, physics. Plastic has to catch light: a highlight along the edge, a micro-shadow under the chip, a faint fingerprint. A phone shot, not a render Sent the draft for approval. The client looked it over, signed off with zero corrections – final files went out. One pass, no rework. A card is a deceptively simple document. Looks like a rectangle and sixteen digits. In reality it's maths in the number, a tie to the issuer, a current design and light on plastic. Miss any one of the four and the file gets exactly two seconds of attention. Need a card for a specific bank and country? Message us. We'll tell you straight what's realistic for your case – then build it. { all data published with the client's consent} › TG: @mustang_service_ms ( https:// t.me/ mustang_service_ms ) › Channel: Mustang Service ( https:// t.me/ +JPpJCETg-xM1NjNl ) #drawing #card #photoshop #revolut #case
    • ============================================================               CLExt Classic Interlude: v7.80 ============================================================   01. Fixed ValidateLocation handling and player/client position synchronization. 02. Added protection against invalid coordinates and characters falling under the map. 03. Improved XY/Z position and heading validation. 04. Fixed MoveToLocation and MoveToPawn packet conversion and target validation. 05. Fixed TargetSelected, TargetUnselected and MyTargetSelected packet handling. 06. Improved GeoData Z-location handling and disabled unsafe PathNode modifications. 07. Added ExUserInfoInventoryWeight support. 08. Fixed inventory weight and maximum load synchronization. 09. Fixed incorrect 0% inventory weight after character login. 10. Added automatic inventory weight updates after EnterWorld and inventory changes. 11. Added inventory weight packet spam protection and safe weight caching. 12. Fixed BuyList and SellList inventory, slot and weight synchronization. 13. Improved NPC target and Buy/Sell packet validation. 14. Reworked mail attachment inventory and weight validation. 15. Added all-or-nothing mail attachment receiving and safe retry handling. 16. Fixed stackable mail attachment validation and INT_MAX overflow protection. 17. Improved COD Adena validation and post-mail inventory weight refresh. 18. Improved Warehouse Deposit and Withdraw validation. 19. Added protection against malformed warehouse item counts, DBIDs and amounts. 20. Added warehouse INT_MAX, CItem and pSID validation. 21. Improved warehouse anti-dupe protection. 22. Reworked the HTML Cache system for improved stability and memory usage. 23. Added lazy HTML loading instead of loading ~20,000 files during startup. 24. Fixed HTML Cache startup crashes with large HTML collections. 25. Added thread-safe HTML Cache access and Clear/Reload support. 26. Added bad allocation, invalid HTML and oversized HTML protection. 27. Reduced HTML Cache RAM usage, startup allocations and disk I/O. 28. Added HTML Caching ON/OFF with live HTM loading support. 29. Fixed ToggleCachingHook and added VS2005-compatible live HTML handling. 30. Fixed ShortcutInit processing and skill synchronization order. 31. Improved shortcut item validation, augmentation handling and va_list safety. 32. Added LiveMode Ability Point system. 33. Added inventory-item-based Ability Points with configurable pointItemId. 34. Preserved the original level-based Ability Point system as fallback. 35. Fixed incorrect Ability Point display and inventory synchronization. 36. Improved Ability skill learning and point validation. 37. Improved OfflineShopRestore loading and FakePC/DBID handling. 38. Added safer OfflineShopRestore socket limits and batch processing. 39. Prevented thousands of restore sockets from loading simultaneously. 40. Added delayed, non-blocking OfflineShopRestore after server startup. 41. Improved OnEnterWorld initialization order and stability. 42. Improved inventory weight, SkillList and acquired-skill initialization after login. 43. Added VIP integration to the EnterWorld process. 44. Added safe UserExtData initialization without modifying the native User structure. 45. Improved duplicate Bronch Jewel and equipped-slot protection. 46. Improved Bracelet, Belt, Bronch and general UseItem validation. 47. Improved general packet, UserSocket, User, pSD and Creature validation. 48. Added safer INT32/INT64 packet handling and malformed-packet protection. 49. Improved L2Server startup memory usage and lazy resource loading. 50. Reduced unnecessary startup allocations. 51. Improved account-only KeyEngine authentication and remote account validation. 52. Removed account expiration-time requirements. 53. Added updater/restart design without requiring CLExtUpdate.exe. 54. Improved CLIEXT HWID, shared-memory and client/server version validation. 55. Improved ReadFile/WriteFile hooks and MemoryProtector handling. 56. Added UoPilot and Extreme Injector detection handling. 57. Reworked VIP point loading, saving and database synchronization. 58. Fixed VIP Level 0 initialization and first VIP activation. 59. Fixed vip.htm activation after login and from party-shared points. 60. Fixed VIP points being incorrectly reset before successful activation. 61. Improved VIP progression from Level 1 through Level 7. 62. Added proper VIP Level 7 MAX/DONE behavior with no Level 8 requirement. 63. Disabled further VIP point collection after reaching maximum level. 64. Reworked VIP BonusInfo/ReceiveVipInfo packet synchronization. 65. Fixed VIP tier, points, duration and level requirement packet fields. 66. Added VIP duration, tier, point and User validation protections. 67. Added safer 64-bit VIP EXP and party EXP calculations. 68. Preserved subclass maximum EXP protection. 69. Improved ItemDataEx validation during character loading. 70. Fixed augmentation loss during login, relog and server restart. 71. Added safe restoration of augmentation IDs directly from the database. 72. Added CItem, pSID, pExItem and User validation during ItemDataEx loading. 73. Improved Shadow Item mana and item lifetime loading. 74. Preserved item protection timeout data during character loading. 75. Added augmentation loading diagnostics and protected valid augmentation data. 76. Preserved database value 0 for genuinely non-augmented items. 77. Added RaidBoss Status synchronization with the World Map. 78. Fixed alive/dead RaidBoss status updates after spawn and death. 79. Added RaidBossStatus as the source of truth for RaidBoss map packets. 80. Fixed RaidBoss map status synchronization after server/database loading.
    • 🚀 L2AQUILA — GRAND OPENING TOMORROW! Lineage 2 Gracia Final — Like L2 Pride, but fresh. The server you've been waiting for opens tomorrow, Saturday 19/09, 16:00 (Greek time) — No Wipe · 24/7 · Anti-DDoS. ⚔️ What's inside: • EXP 9300x · SP 3000x · Adena 5500x · High drop • Max enchant +20 · Safe +3 · 24 buffs / 3 debuffs • 20 free Custom Coins for every new player on day one! • Custom farming zones (Cave of Trials, Cemetery, Ruins of Despair + more) • PvP Events · Olympiads · Offline Trading · Weddings · Balanced classes • Starter + Dynasty shops in every town — playable from minute one 📥 Download: Client + Patch at https://l2aquila.com/index.html 💬 Discord: discord.gg/5ZyBRvG4k · Facebook: facebook.com/l2aquila Be there at opening hour — bring your squad. See you at the Grand Opening! 🔥
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..