Open odisk777 opened 1 week ago
This could be related to an existing issue: https://github.com/opentibiabr/canary/issues/2456 ? Involving Wheel of Destiny.
Enable mount in pz will solve this issue
I have encountered this bug a few times while hunting demons with a low-level paladin. An additional detail is that when I leveled up, my speed became 10 instead of the 65k value. Also, the high speed is not considered a buff, so it can hold other modifiers like haste or slow. It only reverts after a disconnection.
I think it might be related to using utito tempo san along with receiving another speed modifier, which decreases the character's speed even more, potentially creating a negative number. This might explain the 65k speed if it is stored in a 2-byte unsigned variable. Disabling slow after casting utito tempo san resolved the issue where I play.
I can't provide detailed information using a Canary code example because I am unfamiliar with tibia programming.
I have encountered this bug a few times while hunting demons with a low-level paladin. An additional detail is that when I leveled up, my speed became 10 instead of the 65k value. Also, the high speed is not considered a buff, so it can hold other modifiers like haste or slow. It only reverts after a disconnection.
I think it might be related to using utito tempo san along with receiving another speed modifier, which decreases the character's speed even more, potentially creating a negative number. This might explain the 65k speed if it is stored in a 2-byte unsigned variable. Disabling slow after casting utito tempo san resolved the issue where I play.
I can't provide detailed information using a Canary code example because I am unfamiliar with tibia programming.
but this should not normally happen even if it is a visual error because it would be confusing for the user.
Priority
High
Area
What happened?
hi guys. I don't know if you guys are getting this bug in the palandi on speed, anyone else have this problem please report it !
youtu.be/M2e6aqpwY1g
What OS are you seeing the problem on?
Linux, Windows
Code of Conduct