Latest update bug

[Edgewood411 6]

Hi Droidz, 

Since the latest update there's been a weird bug where the bot will be in combat with mobs/creatures and just completely ignore, even pulling more mobs. I have disabled all plugins/used both quester and grinder and it occurs with both iterations of the bots. The bot only seems to attack things that are specifically in the profile for it to attack. But if you are walking from say XR to camp turajo to turn in a quest, it will get attacked the entire way there and not attack any mobs. In Stonetalon charred vale area, it was killing harpies for the quest but aggroing other white harpies and completely ignoring them. It would also pull other harpies for the quest WHILE still being in combat with other white harpies, refusing to attack them. 

 

EDIT- just to add, many other people ive talked to in discord have had this problem with the bot since the latest update. Also it seems that the icon was updated with a tiny red indicator at the bottom left hand? Could this possibly be a beta version that got released pre-maturely? 

[terpfiend 0]

Experiencing all of this as well. I actually did the harpy quest in the charred vale area today and noticed this behaviour. I've messed around with a couple different profiles/FCs/plugins and it seems to be completely random on when it decides to work correctly.

[gearshifter 3]

ditto ><

[Marsbar 228]

I've been having these issues too, thought it might be my fightclass but as you guys are getting it too, it must be an issue.

[Droidz 2738]

Hello, you get all this problem in WRobot for vanilla? (or you use others wow versions)?

[terpfiend 0]

21 minutes ago, Droidz said:

Hello, you get all this problem in WRobot for vanilla? (or you use others wow versions)?

Yes I believe we are all using vanilla, though I'm not 100% about the other commentors.

[Edgewood411 6]

Yes all these problems are in vanilla

[Droidz 2738]

Ok, I have check code change and I don't found what can cause this problem, if you can share log of sessions where you get this problem (more I have log files, better is it).

[Marsbar 228]

I think it may be to do with blacklisting - i was only really getting this on my rogue and i think its because it auto blacklists the mob if I stealth towards it too slowly.

[Matenia 628]

I haven't really had these problems on vanilla.
If any of you use my plugin - about a month ago or so, there was a small bug in it where sometimes it wouldn't disable Conditions.ForceIgnoreIsAttacked again, that COULD have lead to this behavior.