Still a work in progress. I *think* the evo item structure is inserted at 82 judging from below (otherwise it will be the Ornament ID if present):-
Just a brain dump regarding ItemSerializationHeader, based on packet captures on COTF client. It should give *some* indication for earlier clients, although it could get painful trying to backport, esp. pre- ROF:-
Evo items (which have an unknown int32 NOT unint or byte at position 43 which is >0) have an extra 25 bytes in the header, I think at position 82.
If there is an ornament, the id file (IT12345 etc) for the ornament is placed BEFORE the item name (e.g. in ItemSerializationHeader) , 75 bytes away from the 1st "unkn_string". If it is an evo item, there is 25 bytes of extra info BEFORE ornament id, so it starts at 107.
Non evo item, no ornament= ItemSerializationHeader= 110 bytes
Non evo item, ornament= ItemSerializationHeader= 117 bytes. Ornament ID File @ 82
evo item, no ornament= ItemSerializationHeader= 135 bytes
evo item, ornament= ItemSerializationHeader= 142 bytes,Ornament ID File @ 107
For all evo items I have seen so far, regardless of ornamentation or not:-
Evo id (duplicate of Lore group Id, but only stored here for evo items) stored at 82
current evo level= 98 (byte)
evo level max= 99 (byte)
evo xp=94 (% expressed as single, luckily not the mad EQ19 thing)
|
Hybrid Mode
