Quest Physical Training: Forced Labor---Hyjal 80-82 H profile, line 2624. <CustomBehavior File="InteractWith" QuestId="25509" PreInteractMountStrategy="Dismount" InteractByUsingItemId="54788" MobId="202952" NumOfTimes="1" NonCompeteDistance="10"> <HuntingGrounds> <Hotspot X="4497.652" Y="-4274.71" Z="904.4438" /> <Hotspot X="4489.638" Y="-4207.516" Z="917.9042" /> <Hotspot X="4462.573" Y="-4161.2" Z="931.2515" /> <Hotspot X="4557.5" Y="-4116.103" Z="944.2537" /> <Hotspot X="4567.564" Y="-4168.217" Z="914.8597" /> <Hotspot X="4610.544" Y="-4249.458" Z="903.1671" /> <Hotspot X="4688.793" Y="-4263.408" Z="900.4235" /> <Hotspot X="4729.933" Y="-4338.116" Z="895.1566" /> <Hotspot X="4696.564" Y="-4383.854" Z="895.7845" /> The bot tries to use the quest item but it says "Out of range" continually , till it ignores that node(quest object) and flies to the next hotspot. After several failing tries I just manually completed it, I don't know if it would continue like that indefinitely. Tried to look for some info on "Noncompetedistance" , as changing its value could solve it (just wondering) but found nothing. EDIT: Exactly the same issue (out of range when trying to use a quest item on a target) on quest Battlefront Triage , deepholm H profile.
Hi, Kasia, [08:33:30.078 D] Goal: Goal: Collect Trident of Naz'jan x 1 [08:33:30.079 D] Changed POI to: Type: Hotspot, Loc: <1479.762, 5411.915, 38.13208> [08:33:30.145 D] Activity: Moving to hotspot ... [08:36:41.904 D] Clearing POI - Reason Waiting for loot flag [08:36:41.904 D] Cleared POI [08:36:43.178 D] Updating repair cost for current equipped items. New value: [0g55s97c] ...<end of log>... Your log just ends abruptly. It looks like Honorbuddy is no longer executing the directive it was given. This is not a profile problem, and should be reported in the Support forum. cheers, chinajade [size=-2]Ref: Kasia's original post w/log[/size]
Hi, Bounty, I believe you will find your question answered in the FAQ. If you are having a specific problem with the profile, please see the guide for Reporting Problems or Seeking Assistance. cheers, chinajade
Hi, Haetur, and thanks for the log. [17:03:11.768 D] Goal: Picking Up Quest - Speak With Spraggle : QuestID - 24794 : To - Krakle : ID - 10302 [17:03:11.776 D] Changed POI to: Type: QuestPickUp [17:03:11.956 D] InteractDebug:599745024 [17:03:11.972 D] Interact Done:599745024 [17:03:14.157 D] InteractDebug:599745024 [17:03:14.172 D] Interact Done:599745024 [17:03:16.339 D] InteractDebug:599745024 [17:03:16.355 D] Interact Done:599745024 [17:03:18.556 D] InteractDebug:599745024 [17:03:18.573 D] Interact Done:599745024 [17:03:20.748 D] InteractDebug:599745024 [17:03:20.765 D] Interact Done:599745024 [17:03:22.954 D] InteractDebug:599745024 Have you by any chance done quests manually in this zone? If so, then that will sometimes alter the toon's quest state and prevent other quests from becoming available. If this is the case, then you will not be able to recover from this, and will need to edit the profile. If you have done some quests manually in this zone, then please edit out the "Speak with Spraggle" quest chain. Make it look like this: <!-- <PickUp QuestName="Speak With Spraggle" QuestId="24794" GiverName="Krakle" GiverId="10302" /> --> <!-- <TurnIn QuestName="Speak With Spraggle" QuestId="24794" TurnInName="Spraggle Frock" TurnInId="9997" /> --> You may also need to similarly comment out the "Lost!" quest, since it is part of that chain. If you have not done any quests manually, then let's try one more time to clean out the cache. (You're description indicates you did it correctly the first time, but its all we've left to try). HelpDesk: Cache corruption problems If still no joy, you'll just need to comment out the quest and move on. cheers, chinajade [size=-2]Ref: Haetur's original post w/log[/size]
Hi, Drazylate, We absolutely must have the log for problems like this. The problem could be anything (bad plugin, mesh issues, bad quest state, etc). Only the log will tell us. If you still need assistance, please see the guide for Reporting Problems or Seeking Assistance. cheers, chinajade
Hi, Slite62, and thanks for the log. We see exactly what you speak of... [18:36:41.362 D] Compiling expression 'HasQuest(27398) && (Me.ZoneId == 1519)' @ line 3257 [18:36:42.007 D] Styx.InvalidObjectPointerException: Cannot read a descriptor on an invalid object. at Styx.WoWInternals.WoWObjects.WoWObject.[](UInt32 , Int32 ) at Styx.WoWInternals.QuestLog.() at Styx.WoWInternals.QuestLog.ContainsQuest(UInt32 questId) at Styx.CommonBot.Profiles.Quest.Order.ProfileHelperFunctionsBase.HasQuest(UInt32 questId) at DynamicCondition29.DynamicCondition.EvaluateExpression() at Styx.CommonBot.Profiles.Quest.Order.ConditionHelper..() at Bots.Quest.QuestOrder.ForcedIf.OnStart() [18:36:42.006 N] Unable to evaluate/compile condition in If tag. Please check your profile. I loaded the profile and tested this line specifically, and there is nothing wrong with it. You were also having 'invalid' object pointer' exceptions on the lines preceding this problem. I can tell you this is not a problem with the profile. But, I'm uncertain if the problem is your Honorbuddy installation, or a bug in Honorbuddy itself. Since you indicated you recovered from the situation, there is probably no way to tell for certain. Thanks for letting us check out the situation, tho. cheers, chinajade [size=-2]Ref: Slite62's original post w/log[/size]
Hi, Arm, You attached a log fragment. We also didn't see any issues in the fragment. If you need assistance, please see the guide for Reporting Problems or Seeking Assistance. We will always need the full log attached that captures the issue. cheers, chinajade
Hi, Y2Krazy, and thanks for the log. This bug has been repaired for a very long time. Here's the problem: [Ref: "[Fly][H - Quest] 68-80 [Kick]($Rev: 2065 $)" @line 5144] This profile is now at Rev 2924, so your copy of the profile is horribly out-of-date, and needs to updated. cheers, chinajade [size=-2]Rev: Y2Krazy's original post w/log[/size]
Hi again, Y2krazy, and thanks for the log. [Ref: "[Fly][H - Quest] 68-80 [Kick]($Rev: 2065 $)" @line 5047] Same issue, moving this report to the side until you get a chance to update your profiles. Again, the current Rev of this one is v2924. cheers, chinajade [size=-2]Ref: Y2krazy's original post w/log[/size]
Hi, Pimpampum, There can be a number of reasons for the problem you describe. We are unable to act on any reports that do not have the full log attached. Please see the guide for Reporting Problems or Seeking Assistance. cheers, chinajade
this is true, this guy just add some garbage work for new buddy bots to make people buy it, then he run back to wow Start building your profiles, don't wait anything from him.
Hi guys! Thanks so much for your hard work. I have had issues with the uldum profile becoming stuck at the Traitors! quest Traitors! - Quest - World of Warcraft The bot will sit below the area it needs to reach for the clickable obejct. View attachment 36268 2013-12-12 19.30 - partial.txt Sorry for partial log.
Dunno if it is Honorbuddy or profile... but three chars have stopped questing in the Stranglethorne Vale, at Nesingwary camp with the following mesage: Could not find quest with ID 208! (Or could I: False) Could not create a performable quest objective for objective with ID 3880! Bot stopped! Reason: Could not create current in quest bot! Quest 208 seems to be this one: Big Game Hunter - Quest - World of Warcraft Picking the quest up manually from Hemmet Nesingwary seems to get the bot going again.
Hello i had a problem with the quest city of light in bc profile i removed the quest and continued. "Problem the quest giver doesnt have the quest" EU Server Best Regards
I did indeed do a few quests manually, but did as you said and lined out the quests the bot was failing on. The bot worked for a while, finishing off all quests in Un'Goro until the quest to go to Solithus popped up, at which point the bot began grinding mobs and not moving to Silithus. And honestly not sure if you want the log for that, it's 5 hours of log >:
Hi, Haetur, We always need the log to analyze problems. That's the only way we can tell if the profile is working as intended, or something is interfering with it. If the log is too big, just zip it please. cheers, chinajade
Just realized the problem was likely due to HB loading the 12-58 profile after i reached 58. I thought the next profile would get loaded automatically.