On screen it says that it crashed on packet ID
181
(hex:
0xB5
), which is "cancel walk". It does not make sense.
Cast system you mentioned has a lot of problems reported in PR comments (server crashes, client crashes):
Hopefully this cast system will be acceptable.
github.com
It looks like it's based on old "djarek cast system", which was known for crashing client, when you connected to caster that had a lot of moving players/monsters on screen.
Question:
How often does it crash? Instant when players move to one of wrong floors? After few seconds? After few minutes?
I'm still not sure, if it's problem with:
- login to Cast on given floor
- walking between floors
- walking on given floor
- monsters/NPCs walking on screen (maybe these floors have them more on player screen, server sends just few floors up/down, when you are on X floor)
Things to
TEST:
1. Join to same cast with OTC and Tibia Client. Wait until Tibia Client crash. Check OTC Terminal (CTRL+T).
Are there any errors/warnings about network or creatures?
2. Login to cast of player that is on floor 6.
Does it crash?
3. Login to cast of player that is on floor 9.
Does it crash?
4. Login to cast of player that on floor 9. Teleport this player to floor 6 (by TP on map or by GOD).
Does it crash?
5. [IF 4 did not crash] make step by this player on floor 6.
Does it crash?
6. Do same tests with map that has no monsters and no NPCs. So nothing except our casting player does not move.
Then we will know, if it's problem with map (Tile) streaming from server to client or with creature movement.