I'll get around to fixing these as soon as possible.Hello,
Character Level: 100
Why bother? Well I want to do all the quest achievements eventually and this would speed up the process immensely and please note that some of these issues are possibly because I am level 100 and there would be no reason to fix I don't think just to accommodate level 100's. I'll note if it's a level 100 issue or not.
I have been running the 68-80 questing file. I have so far discovered the following issues with the following quests.
The bot is up to date and the latest revision has been pulled:
QUEST ZONE: Sholazar Basin
Quest: Dread Saber Mastery
Noted Exception: The toon just runs back and forth even if the tiger required is present in front of it.
Quest: Rhino Master Quest
Noted Exception: It will kill the mob required but it will not loot it? Maybe I was impatient because I stopped the bot and looted it myself, but I was watching it for a good 10 seconds
Quest: Part Time Hunter
Noted Exception: The quest requires you to collect items, but it will not dismount to collect and thus just sits there going from spot to spot with the message "You must be dismounted"
Other Info: I was on a flying mount
Quest: Burning The Help
Noted Exception: The quest requires you to go into the water and do the following:
a) Kill the Hydras (5 of them)
b) Wait for the Hydra to use it's move so you can use the quest item (this is also 5 times)
c) The character goes into the river but does not dive and the bot stops prompting the user to manually do it because the mobs are too far away. (I just did this right now).
Quest: Returned Sevenfold
Noted Exception: The bot stops and tells me I am too high to use this item. I am doing it manually.
Other Info: I am level 100 so this is the reason why. I guess this is a non-issue when you are normally leveling, but if the toon ran through the mob it would work regardless of level.
Quest: Exterminate The Intruders
Noted Exception: The bot at one point would continuously mount and dismount for some reason and then the quest would begin to work.
------------------------------------------------------------------------------------------------------------
QUEST ZONE: Icecrown
Quest: Once More Unto The Breach, Hero
Noted Exception: The bot is trying to pick up the quest Once More Unto The Breach, Hero
but what is happening is that the bot is outputting this:
"[InteractWith-c64c78(warning)] [PROFILE ERROR]: Gossip frame not expected--ignoring." <-- It's doing this over and over.
What I did? - I stopped the bot and picked up the quest manually then started the bot again. It then began questing per normal.
Quest: It Could Kill Us All
Noted Exception: The bot is ignoring the mobs required for loot even though they are super close to the character
What I did? I did the quest manually.
Quest: The Air Stands Still
Noted Exception: This is a multi kill quest to kill three named mobs in the Ziggurats. The bot kills the first one but just stands there after. It does not continue on to the next one.
-----------------------------------------------------------------------------------------------------------
As always keep up the great work and if I notice anything else I'll be sure to reply to this thread.
You may want to check this thread.Is there any way for the bot to force check zone level more often? I'll explain this.
I'm running a new toon full heirlooms. Profiles zones are designated like this for example level 10 to 15, level 16 to 21, ecc.. Imagine I'm on this first lvl10-15 zone, since bot levels up much faster because of heirlooms it usually keeps doing lvl 11 quests (that involve level 11 monsters) in a lvl 11-15 zone however I'm already maybe lvl 15. Is there any way to change profiles zones level requirement? Or even force check the profile to change zone more often and force switch to next level profile.![]()
Legion isn't released yet.I tried to load Legion Intro Quest as a horde character, it just flies to middle of orgrimmar and says "waitting for object to appear“ and not doing the quest
Most of the extra profiles on the back aren't maintained - so it's up to the users to report issues regarding them.Does ravenholdt rep lock box pick-pocketing? I tried several of the ones included in this pack and none work?
After update.
[Singular] ... Zone: Tol Barad using my SOLO Behaviors alone
Could not create current behavior in quest bot; exception was thrown, Profile line# 345, Element: <Objective QuestName="WANTED: Foreman Wellson" QuestId="28695" Type="KillMob" MobId="46648" KillCount="1" />
Bot stopping! Reason: Could not create current in quest bot!
Could not create current behavior in quest bot; exception was thrown, Profile line# 381, Element: <Objective QuestName="Leave No Weapon Behind" QuestId="28685" Type="CollectItem" ItemId="62921" CollectCount="12" />
Bot stopping! Reason: Could not create current in quest bot!
HTML:Could not create current behavior in quest bot; exception was thrown, Profile line# 3614, Element: <Objective QuestName="Source of the Corruption" QuestId="9387" Type="CollectItem" ItemId="29113" CollectCount="5" />
[Profile Message]: Compiling Org Quests
Could not create current behavior in quest bot; exception was thrown, Profile line# 1622, Element: <Objective QuestName="Getting the Points" QuestId="34069" Type="CollectItem" ItemId="109056" CollectCount="5" />
Bot stopping! Reason: Could not create current in quest bot!
[Profile Message]: Compiling Talador Quests
[Avoid-d0e779(info)] Installed avoidance system
Could not create current behavior in quest bot; exception was thrown, Profile line# 689, Element: <Objective Nav="Fly" QuestName="Pyrophobia" QuestId="33578" Type="KillMob" MobId="75302" KillCount="1" />
Bot stopping! Reason: Could not create current in quest bot!
[ProfileCompatibilityInfo-d0e779(info)] Uninstalled avoidance system
Latest update broke quests behaviors.
Code:https://www.thebuddyforum.com/honorbuddy-forum/honorbuddy-support/263663-update-broke-quests-behaviors-post2273791.html#post2273791
Thanks for the reports everybody.Confirmed "could not create quest behavior.." error breaks the questbot, happening to me at level 85 on first mop quests. Please fix asap.
This issue should be fixed in the latest update - it was caused by a mistype.Hi all,
I'm not sure if this is the right place to post this and if its not, apologies and please point me in the right direction.
Since the update to v2.6.15902.843 I am having trouble running the Official 1-100 Questing Profile Pack. I haven't changed anything yet it seems to fail loading.
In the console, I am getting the following line spammed repeatably: [LoadProfile-d0e779(info)] Loading profile 'LK\[Fly][A - Quest] LK 68-80 [Kick].xml'
And if I try to load just the specific profile instead of the Auto Loader V2, I get the following error: Cannot load profile! The 'If' start tag on line 12426 position 4 does not match the end tag of 'QuestOrder'. Line 14483, position 4.
I think I have attached my log below (Never done it, so not sure if I have done it correctly), and I have also tried following this guide to clear up my cache in case of corrupted files: Honorbuddy:HelpDesk:Cache corruption problems - The Buddy Wiki.
I'd be really grateful if anyone can help me.
Infallible83
Legion isn't released yet.
See the post I made right above the post you made.i got a fresh install both of HB and windows. U know why i get this error?
[Profile Message]: Compiling Nagrand Quests
Could not create current behavior in quest bot; exception was thrown, Profile line# 131, Element: <Objective Nav="Fly" QuestName="Up and Running" QuestId="34678" Type="CollectItem" ItemId="112963" CollectCount="1" />
Bot stopping! Reason: Could not create current in quest bot!
There is a "Broken Shore" profile, but the Broken Shore isn't Meshed.so the pre patch intro quests are not included?
so the pre patch intro quests are not included?
There is a "Broken Shore" profile, but the Broken Shore isn't Meshed.
So the bot doesn't know how to navigate around the area.
It's not the bot. It's more issues on Blizzard's end.So may be they'll wake up and roll back recent changes, this is not really smart to include not tested engine changes to this release where they needed only to fix HB<>Wow communication with latest patch.