• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!

Protocol errors

ZiumZium

Member
Joined
Sep 27, 2024
Messages
106
Solutions
1
Reaction score
11
Hi. I have quite a lot of errors in the protocol and I don't know how to solve them.

I have TFS 1.4.2 OTCv8 10.98 engine

OTC logs:

1)

ERROR: no thing
at:
[C++]: ?parseTileTransformThing@ProtocolGame@@AAEXABV?$shared_object_ptr@VInputMessage@@@stdext@@@Z

2)
ERROR: no thing at pos:32837 32014 7, stackpos:2
at:
[C++]: ?getMappedThing@ProtocolGame@@QAE?AV?$shared_object_ptr@VThing@@@stdext@@ABV?$shared_object_ptr@VInputMessage@@@3@@Z

3)
ERROR: no creature found to move
at:
[C++]: ?parseCreatureMove@ProtocolGame@@AAEXABV?$shared_object_ptr@VInputMessage@@@stdext@@@Z

4)
ERROR: ProtocolGame parse message exception (457 bytes, 289 unread, last opcode is 0x00 (0), prev opcode is 0x00 (0)): InputMessage eof reached
Packet has been saved to packet.log, you can use it to find what was wrong. (Protocol: 1098)

5)
ERROR: ProtocolGame parse message exception (9228 bytes, 5619 unread, last opcode is 0x00 (0), prev opcode is 0x00 (0)): InputMessage eof reached
Packet has been saved to packet.log, you can use it to find what was wrong. (Protocol: 1098)

6)
ERROR: ProtocolGame parse message exception (281 bytes, 113 unread, last opcode is 0x00 (0), prev opcode is 0x00 (0)): InputMessage eof reached
Packet has been saved to packet.log, you can use it to find what was wrong. (Protocol: 1098)

7)
ERROR: ProtocolGame parse message exception (281 bytes, 113 unread, last opcode is 0x00 (0), prev opcode is 0x00 (0)): InputMessage eof reached
Packet has been saved to packet.log, you can use it to find what was wrong. (Protocol: 1098)

8)
ERROR: ProtocolGame parse message exception (700 bytes, 532 unread, last opcode is 0x00 (0), prev opcode is 0x00 (0)): InputMessage eof reached
Packet has been saved to packet.log, you can use it to find what was wrong. (Protocol: 1098)

9)
ERROR: ProtocolGame parse message exception (9469 bytes, 5606 unread, last opcode is 0x00 (0), prev opcode is 0x00 (0)): InputMessage eof reached
Packet has been saved to packet.log, you can use it to find what was wrong. (Protocol: 1098)




packet.log:

If I should provide you with any files that will help solve these problems, please write. I don't know how to deal with them
 
What changes did you make last
Hi. I have quite a lot of errors in the protocol and I don't know how to solve them.

I have TFS 1.4.2 OTCv8 10.98 engine

OTC logs:

1)

ERROR: no thing
at:
[C++]: ?parseTileTransformThing@ProtocolGame@@AAEXABV?$shared_object_ptr@VInputMessage@@@stdext@@@Z

2)
ERROR: no thing at pos:32837 32014 7, stackpos:2
at:
[C++]: ?getMappedThing@ProtocolGame@@QAE?AV?$shared_object_ptr@VThing@@@stdext@@ABV?$shared_object_ptr@VInputMessage@@@3@@Z

3)
ERROR: no creature found to move
at:
[C++]: ?parseCreatureMove@ProtocolGame@@AAEXABV?$shared_object_ptr@VInputMessage@@@stdext@@@Z

4)
ERROR: ProtocolGame parse message exception (457 bytes, 289 unread, last opcode is 0x00 (0), prev opcode is 0x00 (0)): InputMessage eof reached
Packet has been saved to packet.log, you can use it to find what was wrong. (Protocol: 1098)

5)
ERROR: ProtocolGame parse message exception (9228 bytes, 5619 unread, last opcode is 0x00 (0), prev opcode is 0x00 (0)): InputMessage eof reached
Packet has been saved to packet.log, you can use it to find what was wrong. (Protocol: 1098)

6)
ERROR: ProtocolGame parse message exception (281 bytes, 113 unread, last opcode is 0x00 (0), prev opcode is 0x00 (0)): InputMessage eof reached
Packet has been saved to packet.log, you can use it to find what was wrong. (Protocol: 1098)

7)
ERROR: ProtocolGame parse message exception (281 bytes, 113 unread, last opcode is 0x00 (0), prev opcode is 0x00 (0)): InputMessage eof reached
Packet has been saved to packet.log, you can use it to find what was wrong. (Protocol: 1098)

8)
ERROR: ProtocolGame parse message exception (700 bytes, 532 unread, last opcode is 0x00 (0), prev opcode is 0x00 (0)): InputMessage eof reached
Packet has been saved to packet.log, you can use it to find what was wrong. (Protocol: 1098)

9)
ERROR: ProtocolGame parse message exception (9469 bytes, 5606 unread, last opcode is 0x00 (0), prev opcode is 0x00 (0)): InputMessage eof reached
Packet has been saved to packet.log, you can use it to find what was wrong. (Protocol: 1098)




packet.log:

If I should provide you with any files that will help solve these problems, please write. I don't know how to deal with them
 
Back
Top