- Joined
- Nov 28, 2006
- Messages
- 114
- Reaction score
- 3
Hello,
A while ago I made a post about packets, well I've been looking into it now and then and finally made something working, for a part atleast.
Now according to some tutorials I read is that the packets are read from right to left, little endian and that the first 2 bytes are the 'opcode'/'header'?, correct me if I am wrong.
I am using EMS v79(latest) to figure packets out.
I figured out that the client, after connection, would wait for the server to send 2 packets, which I captured with my own (terribly coded) C# fakeclient.
These packets were those 2.
I also know that "BC 66 FE 0A 60 2A D0 06" are 2 ints or 2 int16's, so I don't think 09 is the opcode?, but rather 0e with 00, but that brings me to my next problem, the second packet doesn't have a 00 as second byte.
So to make it simple, which part of this packet is the actual opcode?
Regards,
Yoni.
A while ago I made a post about packets, well I've been looking into it now and then and finally made something working, for a part atleast.
Now according to some tutorials I read is that the packets are read from right to left, little endian and that the first 2 bytes are the 'opcode'/'header'?, correct me if I am wrong.
I am using EMS v79(latest) to figure packets out.
I figured out that the client, after connection, would wait for the server to send 2 packets, which I captured with my own (terribly coded) C# fakeclient.
These packets were those 2.
Code:
0E 00 4F 00 01 00 31 BC 66 FE 0A 60 2A D0 06 09
60 F9 62 F9 9B 1B 31 BC 66 FE 0A 60 2A D0 06 09
I also know that "BC 66 FE 0A 60 2A D0 06" are 2 ints or 2 int16's, so I don't think 09 is the opcode?, but rather 0e with 00, but that brings me to my next problem, the second packet doesn't have a 00 as second byte.
So to make it simple, which part of this packet is the actual opcode?
Regards,
Yoni.

