Movement stuck detection too sensitive for Caster

Forgot to say which version: Wotlk 3.3.5a

Can confirm that, have the same issue on caster, WotLK 3.3.5 Version.

Same problem here. Seems that it ignores "IsCasting".

If you can wait next update and tell me if problem is resolved

( http://wrobot.eu/bugtracker/movementmanager-randomly-stuck-r444/ )

On 8/17/2016 at 7:22 PM, Droidz said:

If you can wait next update and tell me if problem is resolved

 

( http://wrobot.eu/bugtracker/movementmanager-randomly-stuck-r444/ )

Reinstalled the whole bot with the new update, still having the problem with casters.

Hello, to fix problem temporaly, increment fightclass range or add at spells condition "Target Distance" : "SmallerOrEqual" : Your range. add "c sharp code" condtion at your range spells with code: 

ObjectManager.Target.GetDistance <= wManager.Wow.Helpers.CustomClass.GetRange

I'll try to find solution (but this problem is amplify in wow 3.3.5, I ignore why).

29 minutes ago, Droidz said:

Hello, to fix problem temporaly, increment fightclass range or add at spells condition "Target Distance" : "SmallerOrEqual" : Your range.

I'll try to find solution (but this problem is amplify in wow 3.3.5, I ignore why).

Works okay as a temporarily solution, i really hope you'll fix that problem. ( had to change now every caster FightClass, because of it )

But thanks, for the temporarily fix.

Okay, that solution is worse then the stuck problem, because now the bot is having problems with moving ( patrolling ) units.

You have incremented fightclass range or add  "Target Distance" condition?

9 minutes ago, Droidz said:

You have incremented fightclass range or add  "Target Distance" condition?

I've send you via PM one of my caster FightClass.

http://wrobot.eu/bugtracker/movement-stuck-detection-too-sensitive-for-caster-r487/?do=findComment&comment=3268

2 hours ago, Droidz said:

Hello, to fix problem temporaly, increment fightclass range or add at spells condition "Target Distance" : "SmallerOrEqual" : Your range. add "c sharp code" condtion at your range spells with code: 

ObjectManager.Target.GetDistance <= wManager.Wow.Helpers.CustomClass.GetRange

I'll try to find solution (but this problem is amplify in wow 3.3.5, I ignore why).

That temporarily solution works good, thanks!

But i really hope, that the problem itself gonna get fixed, once you find the bug that it cause.

In next update, I'll add fightclass condition "Target In Combat Range" (add add in spell with hight range).