Bad Opcode, client crash info

[John Adams]

This is for Xinux, since we were just talking about it.

badOpcode.jpg

The first number is the opcode I believe it was expecting, but didn't get it... instead, client got data it didn't expect, hence crash.

The second number is the opcode previously encountered, to try and help track down the crash. At least, that's what I was told. So far, it works perfectly figuring out opcodes that moved a little.



To make this happen, I took the 1096 opcode range, opcode for OP_TitleUpdateMsg (367) and forced it to 366. Loaded world, logged in, crashed cuz 366 is incorrect.

64 is OP_UpdateInventoryMsg, which I have no idea why that was before Titles, unless that's the order in which we load stuff. shrug. shakey example, but you get the idea.

[xinux]

[John Adams]

http://eq2emulator.net/phpBB3/viewtopic.php?f=10&t=1984