5250 Packet Values

[Korvacs]

Im currently mapping all of the 5250 packets which will bring us right upto date once again. Most of them are pretty straight forward and ive already started to update the wiki!

However theres a few values knocking around which ive never seen before, and i was wondering if anyone could provide any suggestions as to what they could be.

Crossed out values have been figured out.

This will be updated.

Char Info - 1006:

Offset 42 - 1522
Offset 79 - 21

Mentor Packet - 2066:

Offset 24 - 999999 (Value cannot be altered, if it is changed the packet is ignored)
Offset 28 - 20100417
Offset 32 - 13660

[Øblivion]

Originally Posted by Korvacs

Im currently mapping all of the 5250 packets which will bring us right upto date once again. Most of them are pretty straight forward and ive already started to update the wiki!

However theres a few values knocking around which ive never seen before, and i was wondering if anyone could provide any suggestions as to what they could be.

Crossed out values have been figured out.

This will be updated.

Char Info - 1006:

Offset 42 - 1522
Offset 79 - 21

Mentor Packet - 2066:

Offset 24 - 999999 (Value cannot be altered, if it is changed the packet is ignored)
Offset 28 - 20100417
Offset 32 - 13660

Well sorry can't help there
But are you gonna end up release these packets? ._.

[Korvacs]

Yes, some are already on the wiki.

[Øblivion]

Originally Posted by Korvacs

Yes, some are already on the wiki.

Sounds cool
Wish i could help

[-Spirits-]

Wish I could understand it. Lol

[Korvacs]

Its not that difficult alot of it is simply experimentation with values, which is how i figured out 90% of the Mentor packet layout. The rest is looking at existing values in the packets and seeing how they relate to the client, for example:

In the mentor packet i originally got caught up with this value:

20100417

It was a uint (4bytes) not a ulong (8bytes) and i had never seen anything like it, when i was poking around in the mentor system on the client looking for anything that could possibly be related, i noticed that the enrolement date was.

2010, 04, 17

And that was that, i was fairly supprised that they would send the date as a number, they usually send such values as a string, but there we go.

The other number,

13660

Was in fact not a ushort (2bytes) as i originally suspected, it was simply the level and class (both 1 byte in size) right next to each other, i had forgotten that they were in the packet.

So its simply about reading and understanding the data that you are given, and then experimenting with empty areas of the packet to find any other values which you couldnt see previously.

[samehvan]

great effort Korvacs (we all used to c u as a great helper)

if i'm allowed to note something if u don't mind ..

take a look at the Character info packet again , i ddnt actually test it but when i read it i guess it will dc the client coz the Packet length is less than the bytes it sends

106 + TotalStringLength

which are 3 strings

106 byte String_Count
107 byte First_Name_Length
108 string First_Name
109 + Pos byte Second_Name_Length
110 + Pos string Second_Name
111 + Pos byte Spouse_Name_Length
112 + Pos string Spouse_Name

i think it should be

109 + TotalStringLength

or

106 + TotalStringLength+StringsCount

or change the position where start to r8 the strings

103 byte String_Count
104 byte First_Name_Length

i am sure u know very much better than me but i thought i might give a hand

[Korvacs]

Typo, opps!

Fixing it now, this wouldnt disconnect the client though, the spouse name would have been trimmed by 3 bytes thats all.

Mistakes belong in the wiki thread though for future reference, this is just about the values im posting.