Itemtype.dat

Arcо · 03/09/2010, 17:57

Did the structure of the itemtype.dat change at all from patch 5017-5165?

herekorvac · 03/09/2010, 21:19

doubt it except possibly with the itemlock issue

Korvacs · 03/09/2010, 21:29

I would say almost certainly yes.

Kiyono · 03/09/2010, 21:33

Well the DatCryptor seems to work so I assume that it didn't change.

~Falcon · 03/10/2010, 18:51

Quote:

Originally Posted by Kiyono

Well the DatCryptor seems to work so I assume that it didn't change.

That would be the encryption, not the actual structure.

I think a couple of values would most certainly have been added, and possibly moved around. That's just my expectations I can't back it up by experience as I despise the latest client and really have no interest in developing servers beyond patch 5017.

~~pro4never~~ · 03/10/2010, 19:30

The structure itself wouldn't be changed. The itemtype.dat has no reference to binding or locking. That's all done in the source/database. They don't have a completely different item for each and every item except with a modified locked/unlocked and bound/unbound.

I haven't used 5165 but I can nearly guarentee it's the same.

What IS different though is tq switched to a different filetype for other things (it wasn't the .dat, they added something else to check) and that is what causes problems and make new gear not able to be added (weapons/armors/garments)

~~pro4never~~ · 03/10/2010, 19:33

No: Structure is what's being talked about.

Eg: a new field representing some new option/stat for items. Think of a database... add new columns and that's what they are talking about. Adding rows doesn't change anything (it just makes it longer). Adding columns though completely changes the 'structure' of the database.

~Falcon · 03/10/2010, 19:35

Quote:

Originally Posted by pro4never

No: Structure is what's being talked about.

Eg: a new field representing some new option/stat for items. Think of a database... add new columns and that's what they are talking about. Adding rows doesn't change anything (it just makes it longer). Adding columns though completely changes the 'structure' of the database.

But surely, the distance between 5017 and 5065, is quite significant, I imagine many things were added regarding items, item lock, bound items, etc etc.

I see where your coming from in regards to source/database, but TQ have a field in the itemtype.dat for the default gem id in an item, what makes you think they wont have a field for whether locked/bound is default true/false?

Surely new columns where added and maybe the order of some changed?

I might actually check when I get time, just to clear my mind.

~~pro4never~~ · 03/10/2010, 20:52

Quote:

Originally Posted by ~Falcon

But surely, the distance between 5017 and 5065, is quite significant, I imagine many things were added regarding items, item lock, bound items, etc etc.

I see where your coming from in regards to source/database, but TQ have a field in the itemtype.dat for the default gem id in an item, what makes you think they wont have a field for whether locked/bound is default true/false?

Surely new columns where added and maybe the order of some changed?

I might actually check when I get time, just to clear my mind.

as far as I can remember, the itemtype was not modified since the release of conquer 2.0 untill 5095++... it seems unlikely to me that they would have modified it after 5095 but it's definitely possible.

The new patches have SERIOUS alterations with items but I think tq completely moved away from itemtype.dat for these changes and moved to a sort of internal database instead.

Why not check? Decrypt an itemtype from 5095 and one from 5165. Count the number of fields and if they are the same then structure has not been changed. If the decryptor will not work on it then the encryption has been changed.

Both simple things to check.

Note: 1.0 encryption of itemtype.dat was completely different and 99 pct sure the structure would have been changed also seeing as items were drastically modified with the addition of enchant/bless and other stuff.

CptSky · 03/11/2010, 01:39

Quote:

Originally Posted by pro4never

[...]Note: 1.0 encryption of itemtype.dat was completely different and 99 pct sure the structure would have been changed also seeing as items were drastically modified with the addition of enchant/bless and other stuff.

The itemtype isn't crypted before the CPs patch. For the structure, TQ just added some new things with the time, but always at the end.

Just compare this...

Code:

111303 CasqueEnFer 21 0 15 0 0 0 0 0 0 0 150 0 0 0 3 0 0 0 0 3998 3998 0 0 0 0 0 0 0 0 1 1000 Aucun
111003 CasqueEnFer 21 0 15 0 0 0 0 0 0 0 150 0 0 0 3 0 0 0 0 3998 3998 0 0 0 0 0 0 0 0 1 1000 0 0 0 0 0 CasqueDGuerrier Aucun 5 0 0 0 0 0 0 0 0 0

Arcо · 03/11/2010, 01:51

Quote:
Originally Posted by CptSky
The itemtype isn't crypted before the CPs patch. For the structure, TQ just added some new things with the time, but always at the end.

Just compare this...
Code:
111303 CasqueEnFer 21 0 15 0 0 0 0 0 0 0 150 0 0 0 3 0 0 0 0 3998 3998 0 0 0 0 0 0 0 0 1 1000 Aucun
111003 CasqueEnFer 21 0 15 0 0 0 0 0 0 0 150 0 0 0 3 0 0 0 0 3998 3998 0 0 0 0 0 0 0 0 1 1000 0 0 0 0 0 CasqueDGuerrier Aucun 5 0 0 0 0 0 0 0 0 0

5017 != 1.0?
Right?

~~pro4never~~ · 03/11/2010, 01:52

Quote:
Originally Posted by CptSky
The itemtype isn't crypted before the CPs patch. For the structure, TQ just added some new things with the time, but always at the end.

Just compare this...
Code:
111303 CasqueEnFer 21 0 15 0 0 0 0 0 0 0 150 0 0 0 3 0 0 0 0 3998 3998 0 0 0 0 0 0 0 0 1 1000 Aucun
111003 CasqueEnFer 21 0 15 0 0 0 0 0 0 0 150 0 0 0 3 0 0 0 0 3998 3998 0 0 0 0 0 0 0 0 1 1000 0 0 0 0 0 CasqueDGuerrier Aucun 5 0 0 0 0 0 0 0 0 0

Ummm was it not encrypted? If you try opening a 1.0 itemtype.dat it's jibberish meaning it needs a decryptor.

CptSky · 03/11/2010, 02:04

Quote:

Originally Posted by .Arco

5017 != 1.0?
Right?

Yes, the 5017 one has the CPs part and I think some other things like the object type. After, it's the patch of the shield that add the color.

Quote:

Originally Posted by pro4never

Ummm was it not encrypted? If you try opening a 1.0 itemtype.dat it's jibberish meaning it needs a decryptor.

Not encrypted, just in binary format... You just need to read the file in binary.

Nullable · 03/11/2010, 03:01

Quote:

Originally Posted by pro4never

Ummm was it not encrypted? If you try opening a 1.0 itemtype.dat it's jibberish meaning it needs a decryptor.

It is not jibberish, looking at the strings that lie there and because there are no newline characters.. this is in binary format

edit: i just said what CptSky said.. lol essentially agree

~~pro4never~~ · 03/11/2010, 08:44

Quote:

Originally Posted by CptSky

Yes, the 5017 one has the CPs part and I think some other things like the object type. After, it's the patch of the shield that add the color.

Not encrypted, just in binary format... You just need to read the file in binary.

Bahhh, I should have realized that. It's been ages since I've actually taken the time to look at it and when I did I was so used to co having it encrypted so didn't think to read as binary. My bad.