I tend to agree with you that it was a bad set of events. The mesh navigation in the area seems a little off. At one point the bot ran all the way out of the bottom of the cave, towards the little town, but gets caught and dismounts to try and fight an ettin. Bad choice for anyone but a healer, tank, or warlock/hunter, hehe. So I pause and then manually get myself outta trouble. Then turn it back on, and where it goes next is directly on a spawn point of an Ettin. Not sure why it wanted to go specifically there. But again, I got past it, and all is well. I have no doubt the whole thing was exasperated by the fact I was a squishy mage dying all the time. lol
Questing/mount adn etc Is there a way to put the bot to automatically do all the quests, even after level 110? And take mounts and so on? If it is possibile, how do i do that? thx
Hi Echotiger, for Quest "The Bears Up There" (The Bears Up There - Quest - World of Warcraft) I had to change two values in custom quest behavior (BearsUpThere.cs) as HB had trouble throwing bears on trampoline. PHP: private const double TRAMP_RIGHT_SIDE = 87; private const double TRAMP_LEFT_SIDE = 98;
Hi all, What should I do to unlock my garrison with my 110 Demon Hunter pls ? 90-92 Frostfire Ridges profile and Boosted 100 Frostfire Ridges do not work for me... Do I have to do it manually ?
Toon swims offshore and dies repeatedly... StormHeim issue. My huntard keeps running swimming out into the ocean and dying. View attachment 836 2016-10-22 09.30.txt
Bonus Objectives Is there anyway you could make the bots do the bonus objectives, that would be clutch asf.!
Mesh problem, or bot problem? I feel like mesh problem, but maybe the bot can help it. Stormheim quests, and I'm doing the quests in Helheim. Keeps pathing, trying to get past Guarm, and just get 1 shot over and over. Not sure why it's even pathing this way as the quests I have are not for over there. Went through this exact area earlier on another character and it worked fine. No idea why it's not working on Mage. Edit: read the log file, and it's trying to move to sell within Helheim, which is causing it to take this weird path which is getting me killed over and over. Interesting. I'll have to clear out my bags a bunch and then restart the bot and chances are the behaviors will be better. Edit2: Cleared out bags, and even finished the 2 quests that I have in the area by hand. Restarted bot, and it still wants to send me right past this Guarm character. Going to finish the rest of the area by hand, and then restart when I'm out of Helheim. Edit3: Restarted when out of Helheim, after finishing the quests by hand, and it still took me to a place to sell. Seems once the sell command is in, it's gonna do it no matter what? Everything went back to normal after it was able to get back to a vendor.
so after hitting 110 manually I started the bot up to do some questing figuring it would head to suramar and grab some gear upgrades for heroics for me......but it immediately headed to azuna and started finishing quest lines there
And even if you specifically loaded Suramar, the only quest it does is the intro quest. None of the actual Suramar quests have been added yet.
Is suramar being added to this package? the language was removed from the first post so now I dont know
Hi guys. Leveling druid 100-110, and now im lvl 109, suddenly, for no apparent reason, give me an error loading the profile. I've tried everywhere ([N-Quest] Highmountain [Echo], [N-Quest] Stormheim [Echo], [N-Quest] Val'sharah [Echo]) , and always is the same. I've done clean install .. This is second druid, first works fine.. both are alliance. I have the latest version of the profiles: Code: [01:48:06.649 D] Starting behavior Bots.Quest.QuestOrder.ForcedWhile. [01:48:06.755 D] Done with forced behavior Bots.Quest.QuestOrder.ForcedWhile. [01:48:06.755 D] Starting behavior Bots.Quest.QuestOrder.ForcedWhile. [01:48:06.822 D] Done with forced behavior Bots.Quest.QuestOrder.ForcedWhile. [01:48:06.824 D] Starting behavior [ForcedQuestPickUp QuestId: 38347, QuestName: Stealth by Seaweed]. [01:48:06.827 D] Added new hook [Combat_Only] a2a7572d-cdf4-449c-b9e4-e6d3639101ca [01:48:06.834 D] Cleared POI [01:48:06.834 D] Goal: Picking Up Quest - Stealth by Seaweed (http://wowhead.com/quest=38347) : From - Colborn the Unworthy (http://wowhead.com/npc=91531) [Ref: "Pickup" @line 1519] [01:48:06.887 D] Moving to Type: QuestPickUp, NavType: Run from <-859.4084, 4301.147, 745.1597> [01:48:07.025 D] [Flightor] Set up for movement from <-859.4084, 4301.147, 745.1597> to <366.4219, 369.7465, 27.5088> [01:48:07.026 D] [Flightor] Failed ground nav from <-859.4084, 4301.147, 745.1597> to <366.4219, 369.7465, 27.5088> with status PathGenerationFailed [01:48:07.026 D] [Flightor] We cannot fly and end location is not reachable by ground from our location. [01:48:07.026 D] Clearing POI: Can not navigate to current POI. [01:48:07.026 D] Activity: Waiting for object to appear to pick up quest from [01:48:07.072 D] Cleared POI [01:48:07.121 D] [Flightor] Failed ground nav from <-859.4084, 4301.147, 745.1597> to <366.4219, 369.7465, 27.5088> with status PathGenerationFailed [01:48:07.121 D] Clearing POI: Can not navigate to current POI. View attachment 2820 2016-10-24 02.47.txt At revision: 5839
Yes. Those profiles were tested heavily with ground mount testers - and they existed long before the flying version was created considering they were made at the beginning of WoD launch when flying wasn't even obtainable. If I had to guess, I've ran at least over 80 testers on the grand treasure profiles. The mount profile was/is fully capable of jumping between gaps without issues as all jumping logic was hard-coded into the profiles. If you're seeing issues then chances are these are all new that didn't exist pre-Legion and may have been the result of Honorbuddy 3's new navigation system. Like I said before, testing these profiles are no longer a priority since Legion content has the highest demand right now. Once Legion content isn't in as much demand, I'll go back and look on these profiles.
Honorbuddy's navigation tries calculating the absolute fastest route to the destination - which usually causes it to hug against walls or edges. If the Ettin was near a wall or edge, that could've been the reason why. A blackspot would prevent that since blackspots tell the bot it can't go that direction. So it would calculate a path around the Ettin instead.
Try manually loading the questing zone profiles. (eg: Azsuna, Highmountain, etc) The auto-loaders will sometimes skip over zones depending on your quest progress which is why it may be ignoring them for you.
This is a known issue currently. The original plan was to remove the quest behavior and replace it with logic that can be modified within the profile. Thanks for the values though! A fix should be live within the next Honorbuddy update.