Bugs Otclient in tfs 1.0 (10.10)

[totolol123]

Hello, I am using TFS 1.0 (10.10) and the last rev of otclient compiled, over the same several problems presenting in protocol ... Whenever I move an item to a container item disappears, it is as if he had already been moved over does not receive the client and also a lot of error in the terminal ... Someone already used the tfs otclient in 1.0 and it worked? Thank you.

PS: Some of the errors are these:

ERROR: Unable to send extended opcode 1, extended opcodes are not enabled
ERROR: ProtocolGame parse message exception (51 bytes unread, last opcode is 114, prev opcode is -1): unable to create item with invalid id 0
ERROR: ProtocolGame parse message exception (10 bytes unread, last opcode is 180, prev opcode is -1): InputMessage eof reached
ERROR: ProtocolGame parse message exception (10 bytes unread, last opcode is 180, prev opcode is -1): InputMessage eof reached
ERROR: ProtocolGame parse message exception (10 bytes unread, last opcode is 180, prev opcode is -1): InputMessage eof reached
ERROR: ProtocolGame parse message exception (14 bytes unread, last opcode is 180, prev opcode is -1): InputMessage eof reached
ERROR: ProtocolGame parse message exception (10 bytes unread, last opcode is 180, prev opcode is -1): InputMessage eof reached
ERROR: ProtocolGame parse message exception (50 bytes unread, last opcode is 114, prev opcode is 29): unable to create item with invalid id 0

 

[Lord Hepipud]

ERROR: Unable to send extended opcode 1, extended opcodes are not enabled

This error can be ignored

ERROR: ProtocolGame parse message exception (51 bytes unread, last opcode is 114, prev opcode is -1): unable to create item with invalid id 0
ERROR: ProtocolGame parse message exception (50 bytes unread, last opcode is 114, prev opcode is 29): unable to create item with invalid id 0

Can you please parse the function of your server which is adding this Network Message? It should add the Byte 0x72 as header.

ERROR: ProtocolGame parse message exception (10 bytes unread, last opcode is 180, prev opcode is -1): InputMessage eof reached
ERROR: ProtocolGame parse message exception (10 bytes unread, last opcode is 180, prev opcode is -1): InputMessage eof reached
ERROR: ProtocolGame parse message exception (10 bytes unread, last opcode is 180, prev opcode is -1): InputMessage eof reached
ERROR: ProtocolGame parse message exception (14 bytes unread, last opcode is 180, prev opcode is -1): InputMessage eof reached
ERROR: ProtocolGame parse message exception (10 bytes unread, last opcode is 180, prev opcode is -1): InputMessage eof reached

This looks weird. The Client is trying to read more data from the stream than he actually receives. Can you please parse the function of your server which is adding byte 0xB4 as header?

Thank you!

~~~~Lord Hepipud~~~~

 

[Summ]

Container bugs have been fixed in my latest commit.
https://github.com/edubart/otclient/commit/778559c7b9cd182f9ce94df6badbce1926df6469

Tell me if you find other things.

 

[totolol123]

see this have new bug!!
https://github.com/edubart/otclient/issues/359

 

[alisonbarbosa]

this happens when I click on the map and try to read a moving letter!
Help me .