I noticed Muad said something about packets not being padded correctly by the core, but I
think they may just be printed incorrectly.
This is an exmpale of a SendStats packet that I printed on the console and logged on the cilent with UOLog.
On the console:
Code:
11002B001A0EDD74656B70726F78790000000000000000000000000000000000000000000003E803E80000
From UOLog
Code:
13:14:45.750 Server -> Client: 0x11 (SendStats), frequ: 1, len: 0x2B
0000: 11 2B 00 00 1A 0E DD 74 65 6B 70 72 6F 78 79 00 ->.+.....tekproxy.
0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ->................
0020: 00 00 00 00 00 03 E8 03 E8 00 00
You can see the Size area of the packet (2B 00) is incorrectly displayed when printed. Perhaps this is only a problem with SetInt16() ?
