Tool Looking for Lineage 2 Classic Client (Protocol 110) dds file

[Notonix]

TL;DR:

I'm looking for DDF files compatible with the Lineage 2 classic client (Protocol 110). If anyone has them or knows where to find them, please PM me. I'm willing to pay for them.

---

FULL POST:

Hey everyone,

I'm currently working on modifying some files for Lineage 2 (specifically for Classic client, Protocol 110), and I'm in need of the appropriate DDF files to disassemble and work with

files like properly EnchantedWeaponFlowEffectData_Classic.dat and others. I've been running into parsing errors with my current definitions, and it's becoming clear that having the correct DDFs for the Protocol 110 version would make this whole process much smoother.
 

Here's what I've tried so far:

1. Manual Creation of DDF Files: I attempted to create my own DDF files based on other data definitions, such as those for armour and weapon groups. Unfortunately, I keep encountering file scan errors at specific rows, particularly involving fields such as Range_1_3 and MeshID_1,etc. Adjusting the data types and making fields optional did not solve the issues.

2. Consulted Similar Files: I reviewed and compared other available DDF files, such as those for armour and weapons, trying to match similar structures, but the parsing errors persist. There might be subtle differences in how the data is structured for Protocol 110.

3. Tried Different Data Types: I've experimented with different data types (e.g., UINT, FLOAT, HEX) for the problematic fields, but none of these changes have worked consistently across all rows.
    

If anyone here has the DDF files for Protocol 110 or knows a good source where I could find them, I would greatly appreciate it. Alternatively, I'm all ears if anyone has tips or tools that might help generate or reverse-engineer these DDFs effectively.
 

Thanks in advance for any help you can provide!

[911reg]

I don't have the proper ddf files sadly, most of them are fucked up in miko's releases (specifically 110 protocol); however, l2clientdat works fine with that client, is there any particular reason why you don't use it?