TFS 1.X+ The monsters on the map are in strange positions. Can it be removed?

[Tibia Idle]

Hello. On my map, a lot of monsters respawn in strange positions where you can't move. What causes the crash. Is there any way to detect them all or remove them at once or do I have to do it laboriously manually? These monsters are probably causing the crash. The log is at the end of the post. Maybe someone will find a way to protect the server from this.

#0  0x00005e4790ba5c58 in Monster::doAttacking (this=0x73095838ebe0, interval=1000) at /home/ubuntu/8.0test-pokompilacji-debugowanie/src/monster.cpp:819
        inRange = true
        spellBlock = @0x730990657490: {spell = 0x7309903392e0, chance = 5, speed = 2000, range = 5, minCombatValue = 0, maxCombatValue = 0,
          combatSpell = false, isMelee = false}
        __for_range = <optimized out>
        __for_begin = <optimized out>
        __for_end = <optimized out>
        updateLook = false
        resetTicks = <optimized out>
        myPos = @0x73095838ebe8: {x = 33189, y = 31678, z = 14 '\016'}
        targetPos = @0x7309931acd58: {x = 33188, y = 31678, z = 14 '\016'}

 

[Me again]

Hello. On my map, a lot of monsters respawn in strange positions where you can't move. What causes the crash. Is there any way to detect them all or remove them at once or do I have to do it laboriously manually? These monsters are probably causing the crash. The log is at the end of the post. Maybe someone will find a way to protect the server from this.




View attachment 85204

#0  0x00005e4790ba5c58 in Monster::doAttacking (this=0x73095838ebe0, interval=1000) at /home/ubuntu/8.0test-pokompilacji-debugowanie/src/monster.cpp:819
        inRange = true
        spellBlock = @0x730990657490: {spell = 0x7309903392e0, chance = 5, speed = 2000, range = 5, minCombatValue = 0, maxCombatValue = 0,
          combatSpell = false, isMelee = false}
        __for_range = <optimized out>
        __for_begin = <optimized out>
        __for_end = <optimized out>
        updateLook = false
        resetTicks = <optimized out>
        myPos = @0x73095838ebe8: {x = 33189, y = 31678, z = 14 '\016'}
        targetPos = @0x7309931acd58: {x = 33188, y = 31678, z = 14 '\016'}

Um , then remove the monsters from that position? ……

 

[Tibia Idle]

No. this won't solve the problem. There will be other monsters that will cause it. The problem seems to appear when the monster attacks empty tiles.

 

[Dercas]

No. this won't solve the problem. There will be other monsters that will cause it. The problem seems to appear when the monster attacks empty tiles.

Removing the monsters won't solve the problem? that's literally the reason for the crashes, so, it will

why the monstesr are there? what map are you using?

are you sure you didn't mess up spawn.xml ?

 

[czaja152]

Hello. On my map, a lot of monsters respawn in strange positions where you can't move. What causes the crash. Is there any way to detect them all or remove them at once or do I have to do it laboriously manually? These monsters are probably causing the crash. The log is at the end of the post. Maybe someone will find a way to protect the server from this.




View attachment 85204

#0  0x00005e4790ba5c58 in Monster::doAttacking (this=0x73095838ebe0, interval=1000) at /home/ubuntu/8.0test-pokompilacji-debugowanie/src/monster.cpp:819
        inRange = true
        spellBlock = @0x730990657490: {spell = 0x7309903392e0, chance = 5, speed = 2000, range = 5, minCombatValue = 0, maxCombatValue = 0,
          combatSpell = false, isMelee = false}
        __for_range = <optimized out>
        __for_begin = <optimized out>
        __for_end = <optimized out>
        updateLook = false
        resetTicks = <optimized out>
        myPos = @0x73095838ebe8: {x = 33189, y = 31678, z = 14 '\016'}
        targetPos = @0x7309931acd58: {x = 33188, y = 31678, z = 14 '\016'}

you had to learn anything before you started making ots.

 

[Danger II]

we ain't in 2007 where invalid spawns could cause such a crash, unless you using some very old engine

 

[Dercas]

we ain't in 2007 where invalid spawns could cause such a crash, unless you using some very old engine

tfs 1.2 could crash even without invalid spawns:
TFS 1.X+ - crash tfs 1.2 (https://otland.net/threads/crash-tfs-1-2.283772/)
TFS 1.X+ - TFS 1.2 crash tile (https://otland.net/threads/tfs-1-2-crash-tile.287330/)

you don't need to live in 2007 to experience crashes :|