Ingame map issue

[azzmckay6]

Good morning OTlanders.

I come here hoping to get some help from anyone regarding an ingame map problem we are experiencing at the minute.
The issue we have is that the map ingame seems to continuously create 'black squares' at random around the map, please see attached picture-


At first we thought the issue was only occurring when teleporting around the map on a GM character.
We then came to the realisation that this wasn't the case, as it was happening to normal characters too.. and as the player tried to relog etc, it seemed to get worse. Please see attached picture-
We cannot seem to figure out the issue, so I have come here in the hope someone can point us in the right direction.

Many thanks

 

[Gesior.pl]

It's OTC. Press CTRL+T to open console. There will be probably a lot of errors about protocol, but only first is important (rest are here, because some packet did not load properly).

Game looks like some old protocol 7.4/7.7. These protocols for sure cannot handle invisible GMs teleporting to player position and becoming visible, and logging on position of invisible GM, which changes visibility. I've debugged it on some 7.x server. In packet with 'add creature' there is no 'stackpos' in protocols below 8.x, so you cannot tell client, which creature is on which stack. Only way to fix it is to resend whole tile with all creatures.

For old clients there were bots that detected invisible GMs (like detecting Stalkers), because RL tibia developers knew they cannot make GM really invisible, so they send GM with hidden name and without outfit to player client. Bot could easily detect that kind of creature and start alarm about invisible GM around.
On protocol 8.0+ they fixed it - changed client and server protocol - and GMs can be 100% invisible. Server does not send anything to player client, when invisible GM appears next to him.
If your server is some 'downgrade', it probably still uses 8.0+ code to do not send invisible GMs to client, but client cannot handle it properly.
If your server handles Stalkers and other invisible creatures with 8.0+ code to do not send invisible creatures to client, every invisible creature may debug client, if it appears, when there are some players 'on stack' (stairs up/down, rope hole up/down).

Your problem may be not exactly GM related. Same issue with black tiles happens when Tibia.dat and items.otb are not compatible with each other and there is incompatible item on screen. It blocks loading rest of screen.

In both cases post error from OTC console.

EDIT:

If it's OTCv8, it saved packets.log file in OTC directory with wrong packets. It's even better than CTRL+T logs and in packets.log you got all previous errors, you don't have to wait for next black tiles problem. Also players can send you packets.log from their client.

 

[azzmckay6]

These images above, none were caused by any gm going invisible or any invisible creatures being placed on the map, as you can see this was venore amazon camp.

Will take a look at otc error page, once done I will post the error code here and hope for some help to resolve our problem.

Many thanks for your reply mate

 

[ScorpionOT]

Can be wrong item attributes, this usually can happen if you:

• Ported map from higher version (8.1, 9.86, 10.98) to 7.7~
• Edited client .dat files and/or .otb and made some mistakes
• Item attributes signature doesnt match .dat and .otb
• Stackable item in .dat is not stackable in otb, or viceversa.

Your debug log will probably have more info, if you can triangulate the positin coordaenates XYZ for the error, you can usually pick up which item is causing the issues and remove it from your OTBM or fix the probleem at the root.

 

[Mateus Robeerto]

This has happened to me before, and the issue was resolved by simply performing a 'reload all' on the attributes. In the item editor, you need to perform a 'reload all' on the 'attributes' in your 'items.otb' file, along with 'spr' and 'dat'. It's straightforward.

 

[boiga]

Thank you to everyone who replied, all very helpful. The issue was indeed mis-matched item attributes between the items.otb and spr and dat files. We got those cleared up in Item Editor and the issue went away. Thanks again!