This is the desync issue!
Basically, the client is perfectly desynced with the server so the next movement action where the bot wants to go is within the dead zone on the server.
As a result, the bot gets stuck because it's trying to move to a location the server is disallowing. We've tried to play with the next click distance, but that can interfere in tight areas where the imprecision of movement cause the bot to get off track and it can't recover. We do have stuck detection code that tries to randomly click out of this scenario, but it looks like it's not working anymore.
The movement logic does need to be rewritten still, since it still has the random issues with some area transitions as you know with Catacombs, so we'll try to add in more fixes for issues like this.
Also, the aura/buff logic changed to hopefully fix some issues. When you get a chance, can yo retest your Tempest Shield stuff that you reported before the forum data was lost? I did see it then, but wasn't able to reproduce it at the time.
