OTClient ERROR: ProtocolGame parse message exception

[Tbol]

TFS 1.2. Any ideas?

ERROR: ProtocolGame parse message exception (2044 bytes, 66 unread, last opcode is 0x10 (16), prev opcode is 0x00 (0)): unhandled opcode 16

packet.log

ProtocolGame parse message exception (2745 bytes, 136 unread, last opcode is 0x0 - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com

protocolgame.cpp

/** * The Forgotten Server - a free and open-source MMORPG server emulator * - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com

 

[Tbol]

bump

 

[Mattzon194]

Facing same situation here, TFS 1.4.2 protocol 10.98

ERROR: ProtocolGame parse message exception (171 bytes, 38 unread, last opcode is 0x00 (0), prev opcode is 0xa1 (161)): InputMessage eof reached
Packet has been saved to packet.log, you can use it to find what was wrong. (Protocol: 1098)
ERROR: no thing at pos:31654 32230 7, stackpos:1
at:
    [C++]: ?getMappedThing@ProtocolGame@@QAE?AV?$shared_object_ptr@VThing@@@stdext@@ABV?$shared_object_ptr@VInputMessage@@@3@@Z
ERROR: no creature found to move
at:
    [C++]: ?parseCreatureMove@ProtocolGame@@AAEXABV?$shared_object_ptr@VInputMessage@@@stdext@@@Z
ERROR: no thing at pos:31654 32230 5, stackpos:1

Tried difference things, refined map, maped on difference ways, this only happens when login out and login at the place around these cordinates if the player has equipment with skills attributes etc... This is so wierd..

 

[chucky91]

It appears that the creature or items was removed before accessing in memory pointer, possibly it was deleted before.

 

[El Bringy]

Facing same situation here, TFS 1.4.2 protocol 10.98

ERROR: ProtocolGame parse message exception (171 bytes, 38 unread, last opcode is 0x00 (0), prev opcode is 0xa1 (161)): InputMessage eof reached
Packet has been saved to packet.log, you can use it to find what was wrong. (Protocol: 1098)
ERROR: no thing at pos:31654 32230 7, stackpos:1
at:
    [C++]: ?getMappedThing@ProtocolGame@@QAE?AV?$shared_object_ptr@VThing@@@stdext@@ABV?$shared_object_ptr@VInputMessage@@@3@@Z
ERROR: no creature found to move
at:
    [C++]: ?parseCreatureMove@ProtocolGame@@AAEXABV?$shared_object_ptr@VInputMessage@@@stdext@@@Z
ERROR: no thing at pos:31654 32230 5, stackpos:1

Tried difference things, refined map, maped on difference ways, this only happens when login out and login at the place around these cordinates if the player has equipment with skills attributes etc... This is so wierd..

Maybe share the protocolgame.cpp function that sends 0xA1 i think thats playerAddStats can't remember

 

[Mattzon194]

Maybe share the protocolgame.cpp function that sends 0xA1 i think thats playerAddStats can't remember

Ty for info, well i tested alot of changes with source, tried to optimize code with "slower loading" etc nothing worked, Then i read the packet.logs and it said something about "tasks/ranking" then it was my task module that messed things up xD.. Good to know for all who may face similar problems, it can even be modules in client/revscripts luas etc.. so wierd but... Problem only appeared in the tp section, if u had some weapons with stats on equipped u could not login again if u logged in some tiles in the tp section... then i revised the task system a bit and solved it...

 

[Bronk65]

Ty for info, well i tested alot of changes with source, tried to optimize code with "slower loading" etc nothing worked, Then i read the packet.logs and it said something about "tasks/ranking" then it was my task module that messed things up xD.. Good to know for all who may face similar problems, it can even be modules in client/revscripts luas etc.. so wierd but... Problem only appeared in the tp section, if u had some weapons with stats on equipped u could not login again if u logged in some tiles in the tp section... then i revised the task system a bit and solved it...

Thanks, I had the same problem, and it was because I left a monster tracker activated with the tibia client, and when I started otclientv8, apart from that error, it didn't kill the monster. I removed the tracker and now it works fine.