BetterSister

i know, that would be expected, but the other if statements are the problem
edit: only happens sometimes, after char delete and fresh char it works again, really weird

I remove "GetHashCode()" (this added bugs to WRobot)

Changed Status to Confirmed
Changed Version to All

Change continent (dead? logout?) seem to clean objectmanager.
Can you try with the new update and tell me if this change something about CPU usage.

Any news on this issue? 

Unfortunately no good news, @BetterSister. Despite swapping to UseScriptOn and adding the script provided by @Droidz above, the character is running to the objects, presumably running the script (and waiting 5000 ms), then moving to the next object. It does not even attempt to interact with the quest objects. Tested on multiple quests in multiple zones on multiple characters, all with the same result.
Schaka suggested on Discord to clear my session blacklist to see if that helped, but that did not. I'm honestly at a loss as to why this is happening.

Also faced with this problem, the character dies above the place in the screenshot, but the navigation system doesn't understand that you need to climb the stairs and so the character rests in the mountain. Later it is possible to provide the coordinates of this location if zerokx not write.

I keep note, I look in more detail later if I add or not this option.

use in pulse
var hotspots = new List<Vector3>() { new Vector3(1,2,3), new Vector3(1,2,3), new Vector3(1,2,3), new Vector3(1,2,3), }; var mobs = new List<int>(); if (!Quest.IsObjectiveComplete(1, 12345)) mobs.AddRange(new int[] { 1, 11, 111 }); if (!Quest.IsObjectiveComplete(2, 12345)) mobs.AddRange(new int[] { 2, 22, 222 }); if (!Quest.IsObjectiveComplete(3, 12345)) mobs.AddRange(new int[] { 3, 33, 333 }); var mob = ObjectManager.GetNearestWoWUnit(ObjectManager.GetWoWUnitByEntry(mobs)); if (mob != null && mob.IsValid && mob.IsAlive && mob.IsAttackable) { Interact.InteractGameObject(mob.GetBaseAddress); Fight.StartFight(mob.Guid); return true; } var p = hotspots[Others.Random(0, hotspots.Count - 1)]; GoToTask.ToPosition(p, 5, true, (c) => ObjectManager.GetNearestWoWUnit(ObjectManager.GetWoWUnitByEntry(mobs)) == null); return true;  

Since i couldn't get the settings to save and load i hardcoded the plugin to use only backwards for 1500ms every 2.5s-6s
link: https://drive.google.com/open?id=0BxrnR7sFxoj9OVhfYXlPNmppdmM
Just delete your settings file called MoveDuringCombat-YournameRealmname

Changed Status to Duplicate
Changed Version to All

Hello,
I have start to add events, now you can hook fight class like:
wManager.Events.FightEvents.OnFightLoop += (unit, cancelable) => { if (!unit.IsValid) return; if (unit.GetDistance2D - unit.CombatReach < 10 && unit.GetDistance - unit.CombatReach < 15) { if (unit.IsStunned || unit.Root || unit.Confused || unit.HaveBuff("Concussive Shot")) Move.Backward(Move.MoveAction.PressKey, 1000 * 3); } }; (you need to wait next update).
If you need events/hooks for specific WRobot method, do not hesitate to tell me.

Yes, since Legion pre-patch, he has a lot of buffs passive (or not) with same name, you need to use spell id instead spell name.

You can make list of them and tell the bot this is list of possible debuffs then tell bot to check if there is one of them 
 
TLDR as workaround you need some programming knowledge to do it yourself 

If you can wait next update and tell me if problem is resolved (I cannot completly ignore path in blacklisted zones, but I have improved it)

!ItemsManager.HasItemById(5512) does work for my .cs file. Thanks Sister!

This should be high priority :S i hate spots like this where it gets permanently stuck... Impossible to make flawless quester!

This should be high priority :S i hate spots like this where it gets permanently stuck... Impossible to make flawless quester!

This should be high priority :S i hate spots like this where it gets permanently stuck... Impossible to make flawless quester!

let the clip talk itself
 

Changed Status to Fixed

Couldn't reproduce anymore, seems to be fixed !

Changed Status to Fixed

Impressive work! I'll write more about this after a moment of testing

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