1. What OS you are at?
Windows 10, 64-bit
2. Real PC or VPS?
Real PC
3. Using WindAddons? Which version?
1.6.0-Beta.14
4. Which version of WindBot?
2.9.0-beta.44
5. Which version of Game Client?
Tibia11, latest version
6. Do you have a Dedicated Graphics Card?
???, I guess, nvidia geforcec gtx780
7. Detailed description of the problem.
So I have beenn running for example hive surface with avas and it works fine. Bought a script for fobidden lands and suddenly the char starts blocking two hydras/behemoth instead of running around as it should. According to the creator of the script its probably a WB bug eventhough I told him that all my other area rune scripts works.
Here is the quote from our conversation
You're on Tibia 11, right? I guess it has to do with useitemon(), as the script has nothing telling it to block monsters. You should report that as a Tibia 11 bug.
edited by RoxZin: My script calls pausewalking() before the actual rune shooting. I've made several tests and doing pausewalking(0) after the rune was shot didn't help much, so I changed it and it returns the code as soon as the rune is shot. With Tibia 11, it tends to not move after the rune was shot (it should have 1,5 to 2,2sec as I check if it's able to cast a rune again using runeinfo().cancast, that doesn't seem to help too) as it does on Tibia 10, but rather keeps waiting for the cooldown to shoot again.
9. Do this happen in WindBot for Client Version 10.x too?
According to him it works flawless on tibia10
edited by RoxZin: it doesn't happen on Tibia 10, as the action was designed to it and used on all my Mage scripts.
10. Debug Log.
11. Comments.
I guess using pausewalking(0) after the job is done can "fix" the issue, but I haven't tested that - and as it makes the work slower on Tibia 10, it may also make it slower on Tibia 11.