Were you able to fix this issue or is it on going? Cause I am caught up with it too.. and its non stop. Please get back with me, Thanks.
need help on legion questing! This works really well when it works, it might be an issue on my end, but the bot stops like every other turn in and if I hit start again it will go right back to questing... not sure what thats all about, he will run to an npc either do the turn in and stop or stop before the turn in I have to keep starting it over and over. I always deleted the cache too. This is on legion questing with autov2 or specific zones too doesnt matter.
Anyone else level a monk notice everytime it goes to the class hall it can never figure out how to get to portal, you have to move him about 30 yards every time.
This profile work great on my priest but errors out on my mage and does nothing on my shaman. Attached my shaman log. Any idea what's up? I've tried Auto Loader and Auto Loader v2. View attachment 5584 2016-10-03 20.13.txt
Profile for legion 99% afk. Did handle only chain to go Stormheim. I have started bot on lvl 100, but he is ended on 109 lvl. Did all lines in 4 zones. Here is the best way to improove: Let the bot take quests to dungeons. So when char hit 109 lvl users can just go to some dungeons and level up to 110
Hello I am running this profile and enjoying it up until I received the dungeon quest Wrath of Azshara. The quests calls for me to go into the dungeon w/ group and defeat it, however I do not have time for that. I have tried dropping the quest many times and even starting from different zones, but the autoloader always brings me back to the entrance to the dungeon whether I have the quest or not...any ideas??
Good to hear it's working well! Most of the consistent "stuck spots" will be fixed when the blackspot system is working again.
I think this was because of the Bonus Objective in the area. I'm still smoothing the edges down around Bonus Objective spots - so there's a good chance it's due to the rough edges.
This seems to be an issue brought on by the new navigation system. The treasure it's going after is: Adventurer's Sack The error is most-likely due to the treasure being underwater as HB3 isn't as tolerant to water as HB2 was. If you manually retrieve this treasure, it should go on after that. In the mean time, I'll mark this down as an issue and will look into fixing it when the lower priority profiles will be addressed.
Because the original "Auto-Loader" doesn't check your player level. Hence why it's affixed with "for Loremaster" under the "Quick Start" section. Use "Auto-Loader v2" if you want the loader to check your player's existing level while a profile appropriate for your character is considered.
I honestly have no idea why Kick wrote these profiles with those If statements. <PickUp/> and <TurnIn/> internally check all this stuff, so the <If/> statements themselves are all redundant. PickUp only runs if: You don't have the quest in your questlog, and it's not completed. TurnIn only runs if: You have the quest in your questlog and it's completed. If these conditions aren't met, the lines are ignored. So it being outside of the If tag shouldn't matter either way. I can look into adding extra code to handle the Blizz-end bug. I'll go ahead and mark this down to be investigated if it's not caught and fixed by Hawker - who is currently hard-testing the 1-100 range.
I've swapped out the logic here so that the bot will better handle this quest. Thanks for the report!
I've never had this reported nor have my testers ran across this issue. Given this, I have no basis to debug off of. If you could provide a log, or any technical information from the bot that will better help me understand what exactly is causing the issue - I'll be glad to look into it for you.
There seems to be an issue with your client. Either Honorbuddy or WoW - something is breaking the GreyMagic injection process. Could you try with DirectX9 instead of DirectX11? If that doesn't work - try a fresh install of Honorbuddy.
Progress will come after I'm able to fix all the existing issues in the Artifact Profiles + Singular. Hopefully this will be soon - perhaps within the coming week.
The profiles for 90-100 do not require flying at all. In fact, they were built purely with ground navigation logic. The flight logic that was added after-the-fact is simply "layered" in and has no affect on the original ground navigation. If you're having issues with movement, then this is due to HB3's new navigation system. The profiles are slowly being adapted to fully support the new navigation tolerances of HB3.
I've pushed an edit to the pack that will make the bot farm for the item if you don't have it. And I've also added a HasItem() check prior to running the quest pick up code to ensure the player has the item first. This should prevent this issue from ever happening again.