I've changed the conditions here so it only checks if you have the Elaborate Disc instead of checking for the other items. This should fix/prevent the issue.
had this happen when i went from MoP to WoD. 10 compiler errors encountered in profile '[Fly][A - Quest] 90-92 SMV [Kick] ($Rev: 3946 $)' 'While' xml element on line number 1424 has following errors with code: public System.Boolean __ExpressionFunc__230() { return new System.Func<System.Boolean>(() => Bots.DungeonBuddy.Helpers.ScriptHelpers.CurrentScenarioInfo.CurrentStage.StageNumber == 1)(); } 1) 'ScriptHelpers' does not contain a definition for 'CurrentScenarioInfo' at line 0 'While' xml element on line number 1431 has following errors with code: public System.Boolean __ExpressionFunc__232() { return new System.Func<System.Boolean>(() => Bots.DungeonBuddy.Helpers.ScriptHelpers.CurrentScenarioInfo.CurrentStage.StageNumber == 2)(); } 1) 'ScriptHelpers' does not contain a definition for 'CurrentScenarioInfo' at line 0 'While' xml element on line number 1456 has following errors with code: public System.Boolean __ExpressionFunc__234() { return new System.Func<System.Boolean>(() => Bots.DungeonBuddy.Helpers.ScriptHelpers.CurrentScenarioInfo.CurrentStage.StageNumber == 3)(); } 1) 'ScriptHelpers' does not contain a definition for 'CurrentScenarioInfo' at line 0 'While' xml element on line number 1460 has following errors with code: public System.Boolean __ExpressionFunc__235() { return new System.Func<System.Boolean>(() => Bots.DungeonBuddy.Helpers.ScriptHelpers.CurrentScenarioInfo.CurrentStage.StageNumber == 4)(); } 1) 'ScriptHelpers' does not contain a definition for 'CurrentScenarioInfo' at line 0 'While' xml element on line number 2025 has following errors with code: public System.Boolean __ExpressionFunc__297() { return new System.Func<System.Boolean>(() => Bots.DungeonBuddy.Helpers.ScriptHelpers.CurrentScenarioInfo.CurrentStage.StageNumber == 1)(); } 1) 'ScriptHelpers' does not contain a definition for 'CurrentScenarioInfo' at line 0 'CustomBehavior' xml element on line number 2039 has following errors with code: public System.Boolean __ExpressionFunc__314() { return new System.Func<System.Boolean>(() => Bots.DungeonBuddy.Helpers.ScriptHelpers.CurrentScenarioInfo.CurrentStage.StageNumber > 1)(); } 1) 'ScriptHelpers' does not contain a definition for 'CurrentScenarioInfo' at line 0 'While' xml element on line number 2052 has following errors with code: public System.Boolean __ExpressionFunc__298() { return new System.Func<System.Boolean>(() => Bots.DungeonBuddy.Helpers.ScriptHelpers.CurrentScenarioInfo.CurrentStage.StageNumber == 2)(); } 1) 'ScriptHelpers' does not contain a definition for 'CurrentScenarioInfo' at line 0 'CustomBehavior' xml element on line number 2053 has following errors with code: public System.Boolean __ExpressionFunc__321() { return new System.Func<System.Boolean>(() => Bots.DungeonBuddy.Helpers.ScriptHelpers.CurrentScenarioInfo.CurrentStage.StageNumber != 2)(); } 1) 'ScriptHelpers' does not contain a definition for 'CurrentScenarioInfo' at line 0 'While' xml element on line number 2063 has following errors with code: public System.Boolean __ExpressionFunc__299() { return new System.Func<System.Boolean>(() => Bots.DungeonBuddy.Helpers.ScriptHelpers.CurrentScenarioInfo.CurrentStage.StageNumber == 3)(); } 1) 'ScriptHelpers' does not contain a definition for 'CurrentScenarioInfo' at line 0 'While' xml element on line number 2068 has following errors with code: public System.Boolean __ExpressionFunc__300() { return new System.Func<System.Boolean>(() => Bots.DungeonBuddy.Helpers.ScriptHelpers.CurrentScenarioInfo.CurrentStage.StageNumber == 4)(); } 1) 'ScriptHelpers' does not contain a definition for 'CurrentScenarioInfo' at line 0 Bot stopping! Reason: None Given
Do you have a log for this? Has the bot obtained any artifact weapons at all? Where are you starting the bot?
You're using an extremely outdated version of the profiles. The profile you're loading here is Rev:3946, and the current version is Rev:5593.
Don't post useless posts. I'm extremely busy with fixing these bugs nearly 24/7 especially with the massive amount of work with the Legion profiles, and you posting posts like this do nothing but waste my time.
This has nothing to do with the profiles. Report this as a feature request under the Honorbuddy release section.
Nothing's wrong. Blizzard made the decision that the 4major questing zones won't get you to 110. You have to get to 110 by doing the class hall quests + other artifact quest lines.
It seems that this is a path generation failure for whatever reason. Where was your character standing while this was happening?
This wouldn't be a profile issue. It seems the bot is having issues detecting which mounts your character has.
I've added a faction check to this vendor to prevent Horde characters from using it. Thanks for the report!
There's a path generation error to a specific hotspot. The only way I could debug this is if my tester was in this situation to test changes. I'll remove the hotspot that the path generation is failing on, but I can't guarantee it will fix this.
Thanks for the report + log, but the log doesn't seem to really reveal what happened to cause this issue. This will need to be ran by my testers to see what's going on.
If you were to type: /dump IsQuestFlaggedCompleted(30241) in-game, does this return true or false? If it returns true, then you'll need to clear your cache files as the bot is failing to detect this quest as complete. If it returns false, then it could potentially be a Blizzard issue that this quest isn't showing up. Sometimes a relog fixes this.
My toon is in Stormwind, when profile starts (autoloader v2), it flies directly to Duskwood near /way 77.5, 71.5 After manually traveling to Uldum via portal in SW, my toon went to the flight master, then casted Death Gate (DK talent spell), and then flied to SW again. :S
This may be an issue with the new navigation system - right now there's no solution for this on a profile unless I can get a tester there and recreate it.
Removing this quest isn't a solution since it prevents you from doing anymore quests after it. And leaving it isn't a solution either. Until Blizzard fixes this, it will forever remain a progress-stopping bug. However; I've discovered that the default building chosen by the profile for this zone is the Sparring Arena and this quest won't appear if you don't choose the Sparring Arena. Given this, I've setup the profile to force-choose the Lumber Yard instead. This way the quest can be completely avoided all together.
I believe there's currently a lack of a jumplink on the Mesh for the Death Knight class hall. The bot doesn't know how to use the teleporter that takes you from the first floor to the second and vise-versa. The issue you're seeing is the bot trying to pickup the next artifact weapon quest from Duke Lankral If you pick this quest up and complete the quests up until after you leave the Death Knight class hall, it should then continue on. The jumplink for these teleport pads are being added in very soon.
This is not the correct forum for that question. Usage of that ability would be determined by your combat routine - not the profiles.