not questing hi i try to load the profile but all i get is an error saying Current zone is Azsuna (Azsuna - Zone - World of Warcraft) Can not start quest bot - this profile does not contain a quest order! what is going wrong any help will be great thanks
3rd time reporting this same bug... Quest:Into the Mist - Quest - World of Warcraft & Horn of the Ancient Mariner - Quest - World of Warcraft Bot is doing those quests waaay too long, killing one mob (when there is so many around) mouting up and flying for no reason from hotspots, getting stuck and the end then repeats Just don't tell me this is blizzard end bug
No, this was due to Blizzard deciding to make questing not get you fully to 110. Doing all story lines only get you to 108. The 109 you got was from side quests and bonus objectives. To get to fully 110 you must do all artifact quests + class hall quests.
now im getting this The currently loaded profile does not have anything for the local player to do (is your toon too high level?)
Killing one mob? The profile doesn't tell it how many mobs to kill, that's your combat routine. You need to set the combat routine to pull more mobs.
You should probably just do a fresh install of your bot as none of this stuff is profile error related.
Been getting an error like this almost everyother quest, have fresh installed and everything please help!!!!!! Could not create current behavior in quest bot; exception was thrown, Profile line# 1186, Element: <Objective QuestName="Kung Din" QuestId="29759" Type="CollectItem" ItemId="79753" CollectCount="1" /> Bot stopping! Reason: Could not create current in quest bot!
I noticed a bug in when playing a pally. The bot DOESN'T go to the Sanctum of Light. It only stands at the FP waiting for an NPC to appear that will not appear. You have to go to the Sanctum of Light and open the zone using the scouting map. It also appears that checkpoints are missing in the profile. It refuses to notice that a quest line is already completed. "Tying Up Loose Ends"
"Turn the Keys" in Stormheim always bugs. The quest is complete but my bot runs into the pillars indefinitely. Maybe it has something to do with Runewood's Revenge being incomplete.
Is it possible to force the bot to go to the next zone? The bot just stays at an npc that despawned after the questline was completed. "Waiting for object to appear to pick up quest from" Nothing else happens and nothing shows up in the logs.
Not moving during order hall questline. Playing a Pally and stuck at Light's Heart questline. I thought maybe bot didn't know how to get into order hall or accept quest or get to Exodar but now I am standing in Exodar and still nothing. View attachment 4708 2016-09-15 19.42.txt
"Paid in Lifeblood" in Stormheim also doesn't turn in. My character seems to be swimming out to the open ocean.
The turn in issue hasn't been noted on any testers yet. If it's swimming out in the ocean, then there could be a chance a wrong profile is being loaded. I'll need a log to see what exactly is going on.
The Class Hall loader doesn't do the "Light's Heart" quest line yet. The bot is getting stuck because it's being start in Exodar - it's trying move from your location to quest in Aszuna.
From what I've seen, this is happening in two locations and Blizzard has acknowledged it as an issue on their end. When my testers come to this spot, the way I get around it is to log the character out for about 10-15minutes. After logging back in, the NPCs offer quests again. I'm assuming the issues I've seen are what you're happening - but of course I can't tell without a log. Even if nothing is showing up, the series of events leading up to you getting stuck can be informative as to what happened. But to answer your question - you can go to your order hall and pickup the quest for the next questing area from the command map - after you do that, manually load the profile for the zone that you chose.
A log would tell me what code in the profile is making it run into the pillars and I would be able to fix it.
Checkpoints have nothing to do with that issue. They're only for skipping quests if the player is above a specific level - that way it skips quests that are too low level for the player. Which in Legion everything scales to your level so there's no checkpoints. If it's failing to notice that the quest is completed, then this is a deeper issue not related to the profiles at all. Since you didn't provide a log, I'll add it to my to-do list to manually send testers out to figure out why it's failing to enter the sanctum.