Analyzing packet

[shadowman123]

Well Thx To Fang he Brought me the New Lucky Packet Log 1314 but there was smthing confusing me ill explain what i mean on This Code

Packet 90 -- TQClient -- Length: 24 | 32 -- Type: 1314
18 00 22 05 03 01 01 00 00 00 03 00 31 00 00 00 ;    "

    1   
FF 0A 0B 00 00 00 00 00 54 51 53 65 72 76 65 72 ;   ÿ
     TQServer

well all information i got is That the packet type is 1314 and with length 32 after sealing the packet ...Gr8 but for example the 1st four values 18 00 22 05 03 01 01 00 They Could be 4 ushorts offsets or 2 uint offsets or mixture bet them so how to know that im on the right track ..i h8 Trial and Error So is there any other way ?

[Korvacs]

Seriously how have you managed to get to running a server when you dont even know that the first value in a packet is a short and denotes length and the second value in a packet is a short and denotes the type.

And yes you have to put effort in and use trial, error and your brain to figure stuff out...fml.

[shadowman123]

Originally Posted by Korvacs

Seriously how have you managed to get to running a server when you dont even know that the first value in a packet is a short and denotes length and the second value in a packet is a short and denotes the type.

And yes you have to put effort in and use trial, error and your brain to figure stuff out...fml.

Honestly iam using Public Source and i've Editing on it and learning and i went so far on packets and i knew how it goes and i can build the packet knowing its offsets ..So what i mean i keep learning and im doing good by that

[I don't have a username]

Compare the values in the packet vs the values shown server/client and when/where it's used. Try change the different offsets to different values to get different results.

[_DreadNought_]

I've never been interested in packet logging or analyzing them, never done it either(couldn't care enough, but I recon I could do it with alot of *TRIAL AND ERROR* o.O), but it's been explained to me, and im pretty sure I could see a character UID in there. I dont know if its been done already but dont forget to reverse the values order.

Trail and error is your only option man sorry, dont be lazy.

#edit
you said "That the packet type is 1314 and with length 32 after sealing the packet " Yeah obviously because it says that in plain text.

[Lateralus]

Originally Posted by _DreadNought_

I've never been interested in packet logging or analyzing them, never done it either

...What?!

[Spirited]

I'm pretty sure I wrote a small tutorial on packets. I doubt it's of much use but you can try reading it:

[_DreadNought_]

Originally Posted by Lateralus

...What?!

I know? Sad isnt it, hay, but ive been given tut's on it via msn. :P

I recon I could do it though so it doesnt bother me, I've never really needed to packet log, All the packets I use are out there.