Here's another log from a completely different character that exhibited the exact same issue as I've reported with log...This is now the 4th character that this has happened on: View attachment 10552 2016-10-21 08.55.txt Here is the hotspot that is being moved to that causes the issue: <Hotspot X="3045.282" Y="3367.531" Z="546.4993" /> And removing that hotspot fixes the issue. I'm not sure if this log shows it or it was my previous log, but if the Graymane quest fails to start the scenario on the boat on the start of Stormheim(not HB's fault, it's a known wow bug), the character flies out into the middle of the ocean and dies from fatigue. I've had this happen twice now. I caught it this time and flew back to the boat, abandoned the quest and re-started the scenario. I dunno if there's a way to check if the scenario starts, but it definitely shouldn't fly out into the ocean just to get rez sickness.
Bot isn't interacting with ground targets and instead is just trying to kill mobs to complete objective. Objective would complete much faster if it would interact with Hexxing Fetish. The bot says in the "Info" tab that it will interact with them, but it does not. Goal: InteractWith-Intera: In Progress (no associated quest) Interacting with Hexxing Fetish, MobId(94153), Vilewing Hexer, Cursed Elderhorn, Cursed Prowler [Ref: "[N-Quest] Highmountain [Echo] ($Rev: 5831 $)" @line 1446] Unable to attach log. Going to try again after I post this to try and edit one in. Thank you.
Only the actual 1-110 questing profiles are being worked on at the moment, sorry. The special event profiles aren't of priority at all. You can try using the "version 1" of them to see if they do any better.
I believe my testers have encountered this as well. I'll look into getting a timer added in - thanks for the report!
This could be possible - but would be a lot of work. TurnIn code for each quest would have to be added to the profile - and to add code I'll need to know what quests your player currently as, which is impossible for me to know ahead of time.
The combat routine you're using is spamming so much useless data into the log, it makes it almost impossible to find anything actually useful. It's an absolute mess. Not your fault of course The only thing I see in this log is the bot was waiting 60seconds after attempting to leave Helheim - which then you stopped the bot. I'll run some testers through again to see if they have any weird movement with this quest.
The profiles turn them on. You would have to remove the code from the profiles to prevent this. PHP: <CustomBehavior File="EnablePlugin" Names="Anti Drown" /> If you search for that specific text in the profiles, you can see where it's turned on. Just remove this.
That doesn't seem like a bug - just an unlucky series of events. Right now blackspots don't work in the bot, and the work-around Avoidance logic to make the bot avoid the Ettins was previously causing people to run off the mountain, so it was removed. So in terms of keeping the bot from going near the Ettins - there's not a solution. Not at least until Blackspots are working. I can turn off repairing and vendoring prior to this quest being executed - but that would most-likely cause even more issues. The only thing I could think is to have the bot force-vendor prior to doing any of this quest. That way it doesn't stray off the intended questing path and run into Ettins.
Have you tried a fresh install of the bot? If not, try that - and if the issue occurs again, could you upload a single log of it occurring?
Alright, I'll investigate this hotspot with my testers. In terms of the WoW bug - I've seen this personally as well. There's code to have it loop if it fails to enter the scenario, but it seems the detection is a bit bad - I'll look into improving it. Thanks for the update!
It could be because the InteractWith logic is confusing itself. This seems to be a new issue as of HB3. Before - it properly identify a "enemy" and a "friendly" - and would engage or interact accordingly. Now, it seems to only want to kill stuff, and since the Hexxing Fetish objects are "friendly" - it's not engaging(interacting with) them for this fact. I'm working on a work around for this.
It's because you're using the "autoturnin" addon. That addon will absolutely break questing as it turns in quests faster than the bot's logic can realize the quest is no longer in the player's quest log. Which when this happens, the bot shuts down because it thinks the turn in code failed. Disable this addon then try again. I'd personally also recommend disabling all addons as they could also potentially conflict with the bot.
Bot is getting stuck on trying to accept quest 9792, A message to Telaar This is 100% only bot usage, so I am not sure why it is getting stuck. View attachment 8136 2016-10-21 06.04.txt Edit: Figured it out, I did not have neutral or higher reputation with the Kurenai faction, not sure if profile can be updated to do the 3 quests he offers (which gives you neutral) or just remove the quest entirely.
Did you ever try them on a ground mount? Lots of treasure locations are not reachable, because there is no path to the node and you have to do jumps on your mount this profile isn't capable to do, so it's all just theoretical, but practically it does not work. Example? See log, neverending story of missing the spot, waiting for 60 sec, retrying, failing, ...