Bot stuck at Killing Shatterhorn. It sits there and idle. I think it's because the Tough Ram Meat wasn't converted to Giant Yeti Meat.
Hi,
Memelook, and many thanks for the log and your hint.
[09:02:50.190 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[09:02:50.190 D] Goal: RunLua: In Progress
// Here the profile believes it converted the Tough Ram Meat into a Giant Yeti Meal...
[09:02:50.190 D] Activity: RunLua: UseItemByName(33352) 1 number of times while waiting 1000 inbetween
[09:02:51.329 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[09:02:51.329 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[09:02:51.329 D] Goal: Waiting for 5s
[09:02:51.330 D] Activity: casting 5s
[09:02:51.831 D] Activity: casting 4s
[09:02:52.367 D] Activity: casting 3s
[09:02:53.407 D] Activity: casting 2s
[09:02:54.445 D] Activity: casting 1s
[09:02:55.492 D] Activity: casting 0s
[09:02:56.393 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
// Here the profile uses the Giant Yeti Meal...
[09:02:56.393 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[09:02:56.393 D] Goal: RunLua: In Progress
[09:02:56.393 D] Activity: RunLua: UseItemByName(33477) 1 number of times while waiting 1000 inbetween
[09:02:57.502 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[09:02:57.503 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[09:02:57.503 D] Goal: Waiting for 5s
[09:02:57.503 D] Activity: casting 5s
[09:02:58.069 D] Activity: casting 4s
[09:02:58.606 D] Activity: casting 3s
[09:02:59.706 D] Activity: casting 2s
[09:03:00.809 D] Activity: casting 1s
[09:03:01.888 D] Activity: casting 0s
[09:03:02.525 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[09:03:02.741 D] [QDBG] Starting behavior [ForcedQuestObjective Objective: [GrindObjective MobID: 24178, Count: 1]].
// And here, the profile awaits Shatterhorn to awaken so you can spank it...
[09:03:02.742 D] Goal: Goal: Kill Shatterhorn x 1
[09:03:02.742 D] Changed POI to: Type: Hotspot, Loc: <2638.735, -5057.321, 295.7177>
[09:03:02.793 D] Activity: Moving to hotspot
[09:19:06.573 N] Moving to Type: Hotspot, Loc: <2638.735, -5057.321, 295.7177>
// Obviously, that never happened due to this excessive timeout...
[09:19:21.760 D] Updating repair cost for current equipped items. New value: [0g1s50c]
[09:26:31.822 D] System.NullReferenceException: Object reference not set to an instance of an object.
...
[09:26:31.806 N] Stopping the bot!
[09:26:31.806 D] Stop called!
[09:26:31.806 Q] Bot Stopped! Reason: User pressed the stop button
It appears that the profile is executing the correct directives, but Honorbuddy/WoWclient are dropping the ball somewhere. Without your hint, we would've assumed the profile directives were correctly being carried out as the log implies.
In
v2832, I've restructured the profile directives to retry some things. However, there is no reason to believe that this will actually help if the WoWclient isn't carrying out the issued directives in the first place. Basically, the changes will change the failure mode to "AFKing out", to continuously retrying to assemble the Giant Yeti Meal, and using it on the Yeti.
cheers,
chinajade
[size=-2]Ref:
[post=1311310]Memelook's original post w/log[/post][/size]