Hello profile worked fine from 91-108, but now it says nothing more to do.. I tried to manual load something but it always says the same. He was startung at Stormheim. Finished all other before. [LoadProfile-LoadPr(info)] Loading profile 'Legion\Auto-Loader.xml' Changing current profile to Legion Auto-Loader ($Rev: 5593 $) [LoadProfile-LoadPr(info)] Loading profile 'Class Hall Loaders/[N-Quest] Priest [Echo].xml' Changing current profile to [N-Quest] Priest Class Hall Loader [Echo] ($Rev: 5652 $) Bot stopping! Reason: Nothing more to do.
Which Garrison Quests are you referring to? The questing pack won't do any of the Garrison Scenario quests.
The log doesn't show that any errors are happening, but I do see where the KillUntilComplete behavior stood still for 4minutes. Have you tried a fresh installation?
It was stuck on a quest then - I'd need a log to see why it was. There may have been a bad coordinate somewhere.
So far I've only recorded two of my testers. 1) Night Elf - Demon Hunter, Havoc - 19hours for 98-110. Only stucks was it Fel Rushing off mountains. 2) Alliance Pandaren - Monk, Windwalker - 20hours for 100-110. Only stuck was in Highmountain which was near a big ship. I've added a blackspot that will fix that. These testers run 24/7 under my supervision, so there was no stops.
I have a feeling you are probably aware, but hit 110 in Stormheim, and then loaded the Suramar quests, and it takes my Warlock to Exodar to fight some more demons. The path it takes around Exodar, to click the portals is terrible. Is this a profile issue, or bot mesh issue? This scenario is full of demons, non-stop walking all over the place, and basically the bot gets caught in an infinite fight loop because demons don't stop. Typically after a while, you'll just die from too many of them. Scenario: In Defense of Exodar
There's strange errors being thrown in your log. I believe this may have been an issue with the bot's navigation system - and it should be fixed for the next update. The only thing I could suggest at the moment is try a fresh install.
This seems to be a new issue brought on by Honorbuddy 3. H3 has issues with water sometimes - and the treasure it's getting stuck on is: Adventurer's Sack If you manually get this treasure and start the bot again - it should work. In the mean time, I'm looking to remove this treasure from the profile until better navigation logic can be added for it.
There is a massive wall of errors caused by your quest behaviors. The only thing I could suggest is to delete your bot folder and download a fresh installation. You can get a fresh copy of the bot here: http://updates.buddyauth.com/zips/Honorbuddy 3.0.16279.860.zip Make sure you have your key saved somewhere before you do the fresh install.
Currently the auto-load logic for the class hall profiles isn't all that great. You may want to load the questing zones manually.
When I set this up, I didn't specifically specify a path. There's just a few hotspots with a very high collection distance to detect the portals with. This is typically my method of handling farm zones because it cuts down on bot-trains dramatically and every path is never the same. I've not really been able to test this on multiple characters yet, but the characters I did test it on didn't have much issue. It could have been that the path you got wasn't all too great. What spec was your Warlock? I can send a Warlock tester to there to see if it has similar issues.
Trying to start @ Azsuna but it gives me this error...Any ideas? [Compiler Error]: C:\Honorbuddy\Quest Behaviors\Misc\DMFR_Tonk.cs(322,38) : error CS0117: 'Navigator' does not contain a definition for 'GeneratePath' [Compiler Error]: C:\Honorbuddy\Quest Behaviors\Misc\DMFR_Tonk.cs(355,37) : error CS0117: 'Navigator' does not contain a definition for 'GeneratePath'
The quest behavior DMFR_Tonk is not an official quest behavior, and it's what's giving you issues. Delete this file from your Honorbuddy\Quest Behaviors\Misc folder and it should work again.