BNET FF F3 wtf

[replaced]

when logging into w3xp...

Code Select Expand


SEND
01 FF 50 3A 00 00 00 00 00 36 38 58 49
50 58 33 57 14 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 55 53 41 00 55 6E 69 74 65 64 20
53 74 61 74 65 73 00


Code Select Expand


RECEIVE
FF 25 08 00 95 59 E3 3D FF 50 E7 00 02
00 00 00 EB 20 30 1D 6B 6D 6A 00 00 20
58 7D 99 CB C6 01 76 65 72 2D 49 58 38
36 2D 33 2E 6D 70 71 00 42 3D 31 39 36
34 33 32 34 38 36 38 20 43 3D 31 33 32
39 36 36 32 34 38 34 20 41 3D 32 32 38
36 37 39 33 31 36 20 34 20 41 3D 41 5E
53 20 42 3D 42 5E 43 20 43 3D 43 5E 41
20 41 3D 41 2D 42 00 AF D9 E1 55 3A 73
10 AE 68 FF F3 7A 6A A0 F3 3C F1 A8  <------ FF F3
D3 C9 2D 71 AC ED 57 C9 CC A3 97 59 98
02 A5 FF 40 73 AC 72 C5 AC 09 59 27 32 11
67 E9 77 99 C6 8B 0C F2 15 A9 FA 65 B2 3D
08 25 83 13 D1 4F F5 A7 FD 42 D2 EC FE 5E
46 BC EA 5D 9F 51 69 A5 2A 93 D5 2C A1 CF
6F 23 AC 40 AC D7 15 D1 5B DC CE 32 8D EE
4F 91 1F E4 D2 77 7B E6 EE 8E 18 B0 3D 7F
C9 AC 66 A2 75 F4 D4 29 22 34 C4 8A B0


Code Select Expand


BNET: DISCONNECTED


*dun dun dun*         

ur all (read word below)

[l2k-Shadow]

That's a part of the server signature, not a packet. This is why you don't split your data according to seeing 0xFF.

[UserLoser]

Just because there is a byte of value 0xff doesn't mean it's a new packet.  Like stated above, it's part of the server signature.  When reading documentation and writing the code yourself this is nothing new.

[Hdx]

Code Select Expand


0000 FF 50 E7 00 02 00 00 00 EB 20 30 1D 6B 6D 6A 00
0010 00 20 58 7D 99 CB C6 01 76 65 72 2D 49 58 38 36
0020 2D 33 2E 6D 70 71 00 42 3D 31 39 36 34 33 32 34
0030 38 36 38 20 43 3D 31 33 32 39 36 36 32 34 38 34
0040 20 41 3D 32 32 38 36 37 39 33 31 36 20 34 20 41
0050 3D 41 5E 53 20 42 3D 42 5E 43 20 43 3D 43 5E 41
0060 20 41 3D 41 2D 42 00 AF D9 E1 55 3A 73 10 AE 68
0070 FF F3 7A 6A A0 F3 3C F1 A8 D3 C9 2D 71 AC ED 57
0080 C9 CC A3 97 59 98 02 A5 FF 40 73 AC 72 C5 AC 09
0090 59 27 32 11 67 E9 77 99 C6 8B 0C F2 15 A9 FA 65
00A0 B2 3D 08 25 83 13 D1 4F F5 A7 FD 42 D2 EC FE 5E
00B0 46 BC EA 5D 9F 51 69 A5 2A 93 D5 2C A1 CF 6F 23
00C0 AC 40 AC D7 15 D1 5B DC CE 32 8D EE 4F 91 1F E4
00D0 D2 77 7B E6 EE 8E 18 B0 3D 7F C9 AC 66 A2 75 F4
00E0 D4 29 22 34 C4 8A B0
I added offsets to your packet, Notice that the packet length is 0xE7, and the packet goes all the way down to the 0xE0 line, and it has 7 bytes on that line! 0xE0 + 7 = 0xE7.
Do if you were to extract teh data correctly', everything will be in the one packet and ten you can use the format here to figure out what the part with 0xFF in it means. From 0x68 on is the server signature.

Also, if you are splitting the data by 0xFFs you will get really screwed when you are in the chat channels, MANNY times Diablo II realm charecters will have MANY 0xFFs in there statstring.
Your bot world freak (OMG OMG 1 BYTE PACKETS, WHERES THE PACKET ID!!! OMG OMG)
~-~(HDX)~-~