Just started using this today. I thought it was going to have super fast runs like a real player would 2m-2m30 by mass pulling everything and then just aoeing. Instead it just runs from small pack to small pack. Working as intended?
lol, im guessing u've used echos profiles? it may make sense to make the bot pull large packs of mobs and kill them but its actually quite common for most dungeon farming profiles (like this one) to not do that. developers like echo are slowly setting standards//expectations in dungeon farming profiles. also this profile was posted back in 2012, so its gots some age to it xD
I have indeed used some of Echos mass pulling profiles Guess I'll stick to them until places like this get updated because it's a shame what could be a 2m run is done in 7m+
2 minute runs are pointless though really, as you'll run into the "too many instances lately" crap and you'll have to wait anyways, so longer runs aren't always a bad thing.
Run instance for 30m for your 10 instances an hour (time to go to merch and sell junk) relog, change profile to a non instance farming spot = more gph So it's not useless. It increases your gph. Or what you can do is if you monitor your bot 1 run normal, 1 run heroic = 1hr for the 10 runs high cloth yield no switching downtime of relogging ect ect
Does this profile still work? I walk into the instance after choosing heroic and it doesn't do anything. I have it set for questing bot also.
The bot doesnt go to the vendor, and fly around the doungeon, after the bags are full. He blacklisted the vendors, I dont know why...please help! I havent got any add-ons for WoW. If I fly to Dalaran (without bot) and repair/sell everything and start the bot, he flys to the citadell and stuck the whole time!
I cant seem to use any of your profiles. I place this one and the black temple on on the questing bot and get this nifty skifty message. Any idea on how this can be fixed? The currently loaded profile does not contain a sub profile usable for the current character (is your toon too high level?)
MoveTo failed to move to the location: <5592.983, 2011.288, 798.1511> We are stuck! (<5806.724, 944.2498, 662.9471>) We are stuck! (<5627.336, 1780.161, 816.7399>) We are stuck! (<5493.777, 1999.863, 813.9753>) We are stuck! (<5509.297, 2001.354, 890.5997>) We are stuck! (<5520.285, 2031.535, 895.3486>) We are stuck! (<5505.309, 1963.197, 821.7549>) We are stuck! (<5521.878, 1973.765, 894.8286>) We are stuck! (<5482.765, 2018.37, 823.0533>) We are stuck! (<5511.99, 1950.601, 816.6934>) We are stuck! (<5492.11, 2015.418, 813.7632>) We are stuck! (<5507.239, 2013.848, 889.7035>) We are stuck! (<5504.601, 1949.507, 822.3256>) We are stuck! (<5511.135, 1956.408, 859.4023>) We are stuck! (<5511.895, 1960.618, 893.126>)
After Honorbuddy update, I'm getting questbehavior errors [Compiler Error]: c:\honorbuddy\Quest Behaviors\Development\BallisticVehicle.cs(778,23) : error CS0534: 'Honorbuddy.QuestBehaviors.BallisticVehicle.BallisticVehicle.QuestGoalType' does not implement inherited abstract member 'Honorbuddy.QuestBehaviorCore.XmlElements.QuestBehaviorXmlBase.ToXml(string)' Warning: Errors in quest behaviors! [Compiler Error]: c:\honorbuddy\Quest Behaviors\Development\BallisticVehicle.cs(778,23) : error CS0534: 'Honorbuddy.QuestBehaviors.BallisticVehicle.BallisticVehicle.QuestGoalType' does not implement inherited abstract member 'Honorbuddy.QuestBehaviorCore.XmlElements.QuestBehaviorXmlBase.ToXml(string)' Warning: Could not parse While body node Changing current profile to Pit of Saron Trash Endless Farm Then after I start the profile it stops and says, "Nothing more to do."
I had a similar error with another profile, I solved it by just using a fresh install of the newest HB. Try that if you still have an error I can try fixing it when the US realms are back up since it doesn't seem like this profile is supported anymore...
So hard is delete "Quest Behaviors, Cache, CompiledAssemblies" folders before update do new hb version...
theres quite a large number of people that seem to have issues with this profile, not to mention it hasn't been updated in a while....
PLES HELP Bot stopping! Reason: The current dungeon script has no exit location. Please report to the developer.