• 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!

C++ Tibianic DLL Debug redskull

Malek

Member
Joined
Dec 25, 2009
Messages
99
Reaction score
5
Hey guys i have big problem with tibianic dll client, when my character get red skull, client gonna debugged. Some can help me with this?

Code:
+---------------------------------------------------------------
Debug Assertion 7.72 ContentWindows.cpp 925
Wed Apr 15 13:04:58 2020
Windows Version: 6.2 build 9200 on 2
Graphic Engine: 2
Last Packet Types: 131 180 180 160 162 141 130 161 160 121
Last Packet: 180 016 010 202 039 000 016 050 000 000 100 172 000 037 000 007
Player Position: [172,37,7]
Player.cpp 383: exception occurred, reason:
Player.cpp 456: exception occurred, reason:
Control.cpp 1560: exception occurred (Type = 0), reason:
Control.cpp 366: exception occurred (Force?1:0 = 0), reason:
MainWindow.cpp 127: exception occurred (Surface = 1), reason:
GUI.cpp 1408: exception occurred (Surface = 1), reason:
DialogWindow.cpp 109: exception occurred (Surface = 1), reason:
DialogWindow.cpp 692: exception occurred (Surface = 1), reason:
ContentWindows.cpp 1209: exception occurred (Surface = 1), reason:
GUI.cpp 1408: exception occurred (Surface = 1), reason:
ContentWindows.cpp 925: unknown exception occurred (Surface = 1)
----------------------------------------------------------------

Code:
Debug Assertion 7.72 GUI.cpp 44
Wed Apr 15 03:49:09 2020
Windows Version: 6.2 build 9200 on 2
Graphic Engine: 2
Last Packet Types: 131 180 180 160 120 160 162 141 130 161
Last Packet: 203 016 010 157 039 000 016 050 000 000 100 172 000 037 000 007
Player Position: [172,37,7]
Player.cpp 383: exception occurred, reason:
Player.cpp 456: exception occurred, reason:
Control.cpp 1560: exception occurred (Type = 0), reason:
Control.cpp 366: exception occurred (Force?1:0 = 0), reason:
MainWindow.cpp 127: exception occurred (Surface = 1), reason:
GUI.cpp 1408: exception occurred (Surface = 1), reason:
DialogWindow.cpp 109: exception occurred (Surface = 1), reason:
DialogWindow.cpp 692: exception occurred (Surface = 1), reason:
ContentWindows.cpp 1209: exception occurred (Surface = 1), reason:
GUI.cpp 1408: exception occurred (Surface = 1), reason:
ContentWindows.cpp 925: exception occurred (Surface = 1), reason:
GUI.cpp 44: assertion failed (skin = 4368289), reason:
In(skin,0,LASTSKIN-1)
 
Hmm.. are you sure it's red skull? It looks more like teleport:
Code:
Last Packet: 203 016 010 157 039 000 016 050 000 000 100 172 000 037 000 007
These 2 bytes:
203 016 means that size of packet that crashed client is 203 + 16 * 256 = 4299 bytes
It's very big network packet for Tibia. That big packets are just 2:
1) login to game (send whole screen of game, all tiles and creatures)
2) teleport (send whole screen of new location in game, all tiles and creatures)
first byte of that packet is 010 which in engine is probably wrote in hex format 0x0A which is (example old protocol engine):
function sendAddCreature, but from these 'crash logs' of cipsoft we cannot read anything more.
Cipsoft debug shows first 14 bytes of last packet in moment of crash and this packet has 4299 bytes. To detect problem you need to add 'Cams System' to your server (to save all packets bytes on server) or use OTClient (which do not crash on 'bad packets' and generate nice reports in console).
 
Hmm.. are you sure it's red skull? It looks more like teleport:
Code:
Last Packet: 203 016 010 157 039 000 016 050 000 000 100 172 000 037 000 007
These 2 bytes:
203 016 means that size of packet that crashed client is 203 + 16 * 256 = 4299 bytes
It's very big network packet for Tibia. That big packets are just 2:
1) login to game (send whole screen of game, all tiles and creatures)
2) teleport (send whole screen of new location in game, all tiles and creatures)
first byte of that packet is 010 which in engine is probably wrote in hex format 0x0A which is (example old protocol engine):
function sendAddCreature, but from these 'crash logs' of cipsoft we cannot read anything more.
Cipsoft debug shows first 14 bytes of last packet in moment of crash and this packet has 4299 bytes. To detect problem you need to add 'Cams System' to your server (to save all packets bytes on server) or use OTClient (which do not crash on 'bad packets' and generate nice reports in console).
i try to use otclient but i dont have to have hotkeys active how i can disable it?
 
Back
Top