Update; The issue has been found. WoWQuestStep struct was changed from 76bytes to 360bytes - changes have been made in the next version of Honorbuddy to accommodate for this. Currently the new version is still being tweaked a bit, but once it's good to go - all these "Objective" issues should be fixed.
Hi, I have an error at level 42, I pack mega pack 1-110 (profile), I have this error: Could not create current in quest bot behavior; Was thrown exception, Profile line # 7646, Element: <Objective QuestName = "Smokey and the Bandage" QUESTID = "27458" type = "CollectItem" ItemId = "62028" CollectCount = "1" /> I saw the need to replace a file copy paste, but the only dossier is Quest Behaviors that is in the HB file, but this file is not present in the mega pack 1-110 folder. since I am bad in English, I do not understand how to resolve the concern I 'm sorry but I do not really understand , is it possible to explain step by step what I have to do please ?
Hello! Only Problem's with the Horde Character with the Questing Profiles - 1 to 100! 85-86/87 profiles good Work.. and now only problems..and Honorbuddy Stopps.
Quest:Finding the Survivors - Quest - World of Warcraft Zone: Nagrand Bot stuck on opening cages with prisoners
@EchoTiger: This is still a big problem. Your profile always runs into the same issue - dying at frenzyheart tribe because hb wants to take quests from "Elder Harkek". I know it's a bug on blizzards end, we can't change factions because "Artruis the Heartless" is buggy. I couldn't even change reputation manually, it's RIDICULOUS. Can't you fix it for us? (maybe cancel some quests and look for an alternative) Meaning, you say it's your job and such to repair broken stuff, but ignore this problem because the fault is on blizzards end? No it's not anymore because they probably never fix it. Thank you!
All issues that I could find from these quests have been fixed in the latest update. However, some of these issues are bot-related issues. eg: "Exterminate the Intruders" - this would be a logic inside the bot itself.
I'm fairly certain this one was previously reported and is already fixed. I'll have testers running through that will confirm the fixes. Thanks for the report!
Turning in the quest would be a logic handled by the bot itself. Did something happen in-game to bug the bot out? Sometimes quest frames glitch out and "stick" to the interface.
This was fixed a few days ago. It wasn't trying to pick up quests from this NPC - there was an issue where an InteractWith was setup with the wrong mobId / XYZ.
The Legion profiles are already included on the pack. However, none of them have been tested at all. They will work for the most part, but they will probably be very buggy in some places. Not to mention the Mesh for Legion will also need to be worked on. It may be a few days before the Legion profiles are actually AFKable. I'll be setting up a "Tracker" on this thread that details the status of them and how buggy they may be. Once Legion launches, I'll be testing them as much as possible to immediately address all present issues.
[LoadProfile-d0e779(info)] Loading profile '[N - Quest] Legion Intro Quests [Echo].xml' XML Error: Unknown tag "InitOrder" (Input: "<InitOrder> <!-- Perhaps add detection for loading the class hall if player hasn't unlocked this zone yet. --> <CustomBehavior File="Misc\RunLua" Lua="SetCVar('AutoLootDefault', 1)" /> <CustomBehavior File="EnablePlugin" Names="Anti Drown" /> <CustomBehavior File="EnablePlugin" Names="Refreshment Detection" /> <CustomBehavior File="Misc\ProfileCompatibilityInfo" AllowBrokenAddOns="true" AllowBrokenPlugIns="true" /> <LootMobs Value="true" /> <TargetingDistance Value="45" /> <!-- Use LevelBot default --> </InitOrder>") in "HBProfile"! - On line 22 I get this msg when I use legion auto leader and then it does nothing.