Closed ghost closed 7 years ago
That packet is perfectly valid, and can be read using the Packet Parser. It also doesn't include a string, which is why I don't see how it would cause the exception.
EDIT: I'm sorry I think I actually gave you the wrong packet! I read the file backwards. Main posted updated as well.
Send@06:22:35.442 0000AA4100100000000020B6070200030000005E01000621EC12
The reason this failed was that the packet was simply invalid. I don't know how that happened, but Pale's behavior was correct. The problem would probably lie with Morrighan if anything, but since this never came up again, I'll assume it was either a one-time glitch or the issue was fixed.
Packet: