JayMeazy
Member
- Joined
- Sep 7, 2020
- Messages
- 92
- Solutions
- 2
- Reaction score
- 24
Hello, I'm trying to understand how to track down debugs, using the values to go to the offset of the problem is what I imagine you do. This debug, I'm not sure why it happens, I think what I'm gathering is maybe something to do with a mount/outfit change. It should be noted that I made the server support 10.99 by just changing it to 1099 in the protocollogin, so that I could include 1098 in the otclient that I packed, and then I put my custom client in 1099, but it's actually 1098, could this cause problems for everyone? beucase the debug seems to go serverwide after something happpens, but eventually you stop debugging, but you don't get any login information in server log, here is debug info:
here's what otclient says, if you want the 1098 version i'll have to wait until it does it again.
here's what otclient says, if you want the 1098 version i'll have to wait until it does it again.
Code:
ERROR: ProtocolGame parse message exception (11643 bytes, 0 unread, last opcode is 159, prev opcode is 141): InputMessage eof reached