Isle of Thunder today, on the way to "The Court of Bones" the bot didn't mount, walked the entire island and ignored all mobs beating on it, resulting in a couple of deaths to just pick up the quests.
Will do Brodie, thanks.
Something else that happened, all 4 of my bots doing dailies got stuck both going to the quests and returning from quests to the quest hub on this cart and never used stuck detection (back up, go left/right, jump etc) for minutes until I moved them around myself.
Bot accepted Klaxxi quest "Rampage with the machine", but did not do the quest
Also while doing "Sapfly" quest, bot stopped after collected 1 sample, continued only after i manually touched the movement keys.
I can confirm skipping "rampage with the machine" but my sapfly quest worked fine, if very slow, bot only sits in a single spot waiting for a few specific respawns.
Changing current profile to The Golden Lotus r208
Profile Changer: Load Profile: C:\Users\L\Downloads\Honorbuddy\Daily quests\Profiles\Reputation\TMoPDE\[Rep] Golden Lotus Dailies [Brodie].xml done
Profile Changer: Init Done
[Profile Message]: Compiling Golden Lotus Quests...
[Profile Message]: Starting Setting Sun Garrison
[LoadProfile-v369(info) @line 137]: Loading profile 'Scripts\[Rep] Setting Sun Garrison [Brodie].xml'
Warning: XML Error: Could not parse 'If' body node! - On line 167 - [<If Condition="(HasQuest(30264) && !IsQuestCompleted(30264))">
<CustomBehavior File="Message" Text="Starting Enemy at the Gates" LogColor="Green" />
<CustomBehavior File="UserSettings" QuestId="30264" LootMobs="True" PullDistance="25" />
<CustomBehavior File="FlyTo" X="821.932" Y="2080.49" Z="316.099" />
<CustomBehavior File="ForcedDismount" />
<CustomBehavior File="WaitTimer" WaitTime="3000" />
<CustomBehavior File="Vehicles\MountVehOnly" VehicleMountId="65336" X="821.932" Y="2080.49" Z="316.099" />
<CustomBehavior File="SpecificQuests\30264-VOEB-EnemyattheGates" />
<CustomBehavior File="WaitTimer" WaitTime="8000" />
</If>]
Warning: XML Error: Could not parse 'If' body node! - On line 246 - [<If Condition="(HasQuest(30266) && !IsQuestCompleted(30266))">
<CustomBehavior File="Message" Text="Starting Bloodied Skies" LogColor="Green" />
<CustomBehavior File="UserSettings" QuestId="30266" LootMobs="True" PullDistance="1" />
<CustomBehavior File="FlyTo" X="721.186" Y="2340.127" Z="430.8784" />
<CustomBehavior File="ForcedDismount" />
<While Condition="!IsQuestCompleted(30266)">
<CustomBehavior File="Misc\FixedCannon" QuestId="30266" MinAngle="0.2" MaxAngle="1" VehicleId="64336" Buttons="1" ExitButton="12" />
<CustomBehavior File="Misc\RunLua" Lua="VehicleExit()" />
<CustomBehavior File="WaitTimer" WaitTime="5000" />
</While>
<CustomBehavior File="FlyTo" X="682.0827" Y="2394.73" Z="447.0219" />
<CustomBehavior File="FlyTo" X="741.7631" Y="2342.811" Z="539.0228" />
</If>]
Code:Changing current profile to The Golden Lotus r208 Profile Changer: Load Profile: C:\Users\L\Downloads\Honorbuddy\Daily quests\Profiles\Reputation\TMoPDE\[Rep] Golden Lotus Dailies [Brodie].xml done Profile Changer: Init Done [Profile Message]: Compiling Golden Lotus Quests... [Profile Message]: Starting Setting Sun Garrison [LoadProfile-v369(info) @line 137]: Loading profile 'Scripts\[Rep] Setting Sun Garrison [Brodie].xml' Warning: XML Error: Could not parse 'If' body node! - On line 167 - [<If Condition="(HasQuest(30264) && !IsQuestCompleted(30264))"> <CustomBehavior File="Message" Text="Starting Enemy at the Gates" LogColor="Green" /> <CustomBehavior File="UserSettings" QuestId="30264" LootMobs="True" PullDistance="25" /> <CustomBehavior File="FlyTo" X="821.932" Y="2080.49" Z="316.099" /> <CustomBehavior File="ForcedDismount" /> <CustomBehavior File="WaitTimer" WaitTime="3000" /> <CustomBehavior File="Vehicles\MountVehOnly" VehicleMountId="65336" X="821.932" Y="2080.49" Z="316.099" /> <CustomBehavior File="SpecificQuests\30264-VOEB-EnemyattheGates" /> <CustomBehavior File="WaitTimer" WaitTime="8000" /> </If>] Warning: XML Error: Could not parse 'If' body node! - On line 246 - [<If Condition="(HasQuest(30266) && !IsQuestCompleted(30266))"> <CustomBehavior File="Message" Text="Starting Bloodied Skies" LogColor="Green" /> <CustomBehavior File="UserSettings" QuestId="30266" LootMobs="True" PullDistance="1" /> <CustomBehavior File="FlyTo" X="721.186" Y="2340.127" Z="430.8784" /> <CustomBehavior File="ForcedDismount" /> <While Condition="!IsQuestCompleted(30266)"> <CustomBehavior File="Misc\FixedCannon" QuestId="30266" MinAngle="0.2" MaxAngle="1" VehicleId="64336" Buttons="1" ExitButton="12" /> <CustomBehavior File="Misc\RunLua" Lua="VehicleExit()" /> <CustomBehavior File="WaitTimer" WaitTime="5000" /> </While> <CustomBehavior File="FlyTo" X="682.0827" Y="2394.73" Z="447.0219" /> <CustomBehavior File="FlyTo" X="741.7631" Y="2342.811" Z="539.0228" /> </If>]
Clean install, been getting it every time. Copied over all your quest behaviors and plugins. Thought it was a temp thing after the profilechanger thing got put in so I waited a while, doing fresh installs and updating from the svn but since I'm still having it and it's causing me to skip the golden lotus daylies every day I guess it's time to post. Any ideas? Want a full log?
Did as instructed, same problem. Attached log.
Edit: I'm going to bed after this post so may take some time before I respond again.
It's ignoring the mobs enroute because of a NoCombatMoveTo command, to avoid killing for 20 mins trying to reach the quest hub.
[InteractWith-v461(fatal) @line 1154]: [PROFILE ERROR] Unable to locate ItemId(79104) in our bags
Fatal error. Stopping Honorbuddy.
Stop called!
Bot Stopped! Reason: Fatal error in custom behavior InteractWith-v461.
Removed hook [Combat_Main] 6fada0e8-190a-4f12-811f-246fd06f4d81
Removed hook [Combat_Only] d7024326-b9d2-4201-ae4b-6bd445676074
Removed hook [Death_Main] da6c22b4-a4f5-4070-8598-80739628bc77
Activity: Honorbuddy Stopped
System.Threading.ThreadAbortException: Thread was being aborted.
at Styx.CommonBot.TreeRoot.()
at Styx.CommonBot.TreeRoot.()
System.Threading.ThreadAbortException: Thread was being aborted.
at Styx.CommonBot.TreeRoot.()
Thank you, this seems to have fixed this quest. Now I'm having issue with two new things though. On the golden lotus quests it seemed to have entered an infinite loop from a completed quest task (at [08:42:09.555 D] in the log). Handing in the quest and restarting made it continue as normal until it hit tillers. At tillers it didn't pick up the equipment and then stops the bot, complaining that the item required for the task is missing.Some of the QBs had incorrect "names" to them. They are required to list the path they are in, i.e. Vehicles\MountVehOnly. I made the changes, and pushed them up. Hopefully that's the last of the issues with these.
On the last part of the IOT dailies, I often get rolled by the elite triceratops that pats up and down that one little road. Any way to make the bot avoid that road or the aggro range of that thing all together?
Thank you, this seems to have fixed this quest. Now I'm having issue with two new things though. On the golden lotus quests it seemed to have entered an infinite loop from a completed quest task (at [08:42:09.555 D] in the log). Handing in the quest and restarting made it continue as normal until it hit tillers. At tillers it didn't pick up the equipment and then stops the bot, complaining that the item required for the task is missing.
In fact the first item it complained about missing was the bug sprayer so I picked it up manually and restarted, it worked correctly until it needed the bucket. Picked up the bucket and started the bot again and it stopped from missing the bug sprayer. Picked them both up and observed as it was performing the task. It goes to pick up seeds, tills the dirt, plants it, got a plant with bugs on them, runs to both the pest repellers and uses them, uses the bug spray on the plant, deletes both bug spray and bucket from inventory, plants another plant with bugs, uses both pest repellers, runs to the vintage bugsprayer and picks it up but gets the error about being unable to locate the bug spray while picking the bug spray up.
Sorry, this post is terrible to read.