Kick are you planning to add the " fly in draenor " quest chain too? I mean.. all the stuff you need to do for flying in draenor in new patch
Could you try with a fresh install of your Honorbuddy? It looks like the quest behavior listed in your error may be corrupted. Original Post w/log [Hr][/Hr] Is there any specific reason that you wouldn't have access to the store? Anyone who has purchased an Honorbuddy key should be able to access it. Alternatively, you can use the SVN resource to obtain the profiles: https://subversion.assembla.com/svn/buddy-profiles.honorbuddy/trunk/ Original Post [Hr][/Hr] I had plans to do it sometime in the future once I got some free time, but Kickz may do it. I'll point him to your question. Original Post
i cant download either and when i go to the buddy store it says i dont have an account and to register one but when i try it says it already exists? and i dont know how to make the svn thing. i have forgotten.
Goal: Picking Up Quest - Mission: The Murketh and Shaadraz Gateways (http://wowhead.com/quest=10146) : From - Forward Commander Kingston (http://wowhead.com/npc=19310) [Ref: "Pickup" @line 2334] No matter if I use CavaPlugin nor Kickz, bot is stuck there trying to grab a quest that isn't there. Any ideas?
Hello there Kickazz and crew. Today I found a bug in one of the quests. Quest name: Kaelynara Sunchaser Objective: Speak With Elandra [51.6, 50.5] Combat Kaelynara Sunchaser slain [52.1, 47.5] Bug: When talking to Elandra shes supposed to teleport you into another area where you have to kill Kaelynara Sunchaser. What the bot does is that He teleports in, then teleports out, teleports in, then teleports out. And he kept doing this. Fix: I stopped the bot, went into the portal killed her myself/by hand then exited area, completed the mission started the bot again. I do not know how long time it stood there to be honest. Heres the log:
This sounds like a case of Cache corruption. You may want to give this arcitcle a read: http://wiki.thebuddyforum.com/index.php?title=Honorbuddy:HelpDesk:Cache_corruption_problems There should also be instructions there on how to clear your cache. This should solve your issue. Original Post [Hr][/Hr] Hey! Thanks for the log. I've sniffed through the profile code and noticed that section does in fact loop. However, it should only loop for as long as you aren't inside the bubble. I'll need to run a tester out and verify the detection used to influence the loop. It could perhaps be faulty. Thanks again for the report! Original Post w/log
Hello there EchoTiger, Thanks for your quick reply. However I came across another bug. Quest name: I See Dead People Objectives: Retrieve Bryan Finn's Schematic from Spectral Laborers. Bryan Finn's Schematic Schematic shown to Bryan Finn Bug: Its standing in front of a Large Timber, and doing nothing at all. Cordinates are: 39.8, 52.7 Fix: None yet, doing quest by hand. Killed a bunch of spirits, got the scroll(the plan) Started the bot again. It keeps saying: Moving to Type: Hotspot, Loc: <-743.9869, 2266.446, 28.06207> Log:
Hello Crew again, I encountered another bug. Quest name: Sethe, the Dead God Objectives: Help Anzu defeat Sethe in the Broken Spire. Combat Sethe slain Bug: It has to talk with Sethe and say I am ready. But the bot just stands AFK there. Another bot running the quest had the same problem (Not my bot) Picture here: https://gyazo.com/6aec1b1fdd3fcb52836acd55d18102b3 - If you look close you can see that theres my char and another, that i belive is the bot. Fix: Did the quest manually. This is what the bot spams: [16:40:32.088 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedWhile. [16:40:32.091 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. [16:40:32.091 D] [KillUntilComplete-v2034(debug) @line 1843]: Behavior sees 'done'. Skipping behavior. [16:40:32.091 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. [16:40:32.220 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedWhile. [16:40:32.220 D] Goal: Nothing Log:
That didn't fix the problem, I had to do all the follow up quests manually. It has now happened again with: Goal: Picking Up Quest - Fel Spirits (http://wowhead.com/quest=10909) : From - Assistant Klatu (http://wowhead.com/npc=22430) [Ref: "Pickup" @line 3135]
I'm using a fresh install of honorbuddy and its downloading the mesh from the buddy store. NO svn. I dont have a clue whats going on with it. I've tried multiple fresh installs. It's been doing this for a few weeks now. I haven't changed any settings or anything.
View attachment 7712 2015-08-23 08.54.txt idk whats going on. Do auto loader in SW goes to outland just to portal back to SW then goes to Mount Hyjal and sits there trying to pick up quest from Thrall. Ive done a fresh install and HB is trusted on Kaspersky. Ive manually going into deepholm then start profile but it hearths back to sw takes FP to the other side of the Kingdom then trying to go back to SW
Changing current profile to [A - Quest] EK 5-12 [Kick] ($Rev: 3485 $) [Profile Message]: Compiling Goldshire Quests Could not create current behavior in quest bot; exception was thrown, Profile line# 488, Element: <Objective QuestName="Collecting Kelp" QuestId="112" Type="CollectItem" ItemId="1256" CollectCount="4" /> Bot stopping! Reason: Could not create current in quest bot! Getting this message when i try to start the bot in Goldshire... ?
and i just tried the bot on my 91 mage and got this [Profile Message]: Compiling Org Quests Could not create current behavior in quest bot; exception was thrown, Profile line# 1398, Element: <Objective QuestName="What We Need" QuestId="34822" Type="CollectItem" ItemId="111907" CollectCount="10" /> Bot stopping! Reason: Could not create current in quest bot! help
I don't believe that this is entirely a profile issue since I've seen it occur randomly in other situations before with other profiles and other behaviors. It's hard to pinpoint exactly what's happening when this error comes up, but it seems to be something with the interaction. There's currently an issue up on the internal tracker that addresses objects that have been 'freezing' the bot up. I'm assuming what's causing this issue would be similar to that. Original Post
This issue has actually already been fixed. ^^ If you're using the store version of the profiles, it may be a while before the fix is added in. Thanks for the report though! Original Post