HB ARCHIVES: Honorbuddy Profile Pack--DO NOT DELETE!

Hi again
in the quest Egg Hunt - Quest - World of Warcraft when the bot finds the egg, he dosent wait and defend it, he just pick up mount and fly to another Shadow Cloak Generators. i experienced stuck probelm too. hope i didnt get reported i was outside and i think i get stuck for 2-3 hours .


View attachment 6284 2013-10-28 13.29.zip

Another bug, quest Disassembly - Quest - World of Warcraft after killing the three Twilight Juggernaut - NPC - World of Warcraft bot still want to kill them and stand there chain casting without result because they are immune
log = zipped one

3rd bug ^^, quest Physical Training: Forced Labor - Quest - World of Warcraft seems to be a problem with interactwith, bot don't collect Darkwhisper Lodestone - Object - World of Warcraft

View attachment 2392 2013-10-28 23.23.txt

 

I'm getting something related to unhandled IF statements when I try to load the 12-58 Horde profile.

 

View attachment 2416 2013-10-28 16.40.txt

Not sure which quest it's attempting, but for the Alliance BC profile, one of the first few actual quests in Hellfire, the bot just does loops around a very small area. Doesn't appear to be killing anything as there's no quests mobs in that area, and it's not looting the quest items for one of the quests it's on, so not sure what it's trying to do.

 

Hi, 99-LS1-SS,

As described in Things To Know, you may not use Mixed Mode with questing.

cheers,
chinajade

 

WtLoK first zone:
The quests where you interact with Fizzcrank Fullthrottle requires you to go up and elevator, the profile does not seem capable of doing this correctly. When wanting to go up he stands on the elevator platform, but since he entered after the elevator went up and never jumps he actually never gets on it. When attempting to go down he just stands there, next to it.

 

When it was questing in Halfhill, I thought it was a little weird, but didn't take much notice of it.

Today when I bot at Kun-lai summit, it appears that the bot went to a horde camp to use the mailbox... and got stucked there.

 

I wasn't using mixed mode. I was using quest mode. I used mixed mode about 3 or 4 weeks ago and read that it shouldn't be used so I stopped and haven't used it sense.

 

This Pullback Release that just happened today has messed up all the KICK Profiles.

I Was questing bots in hellfire and zagarmarsh and now both bots have tried to swicth to nagrand and start quests they arent high enough to take.
Both bots level 62, both bots where questing like normal without any issues.
Then pullback release and both bots tried to switch to a zone they cannot quest in ( quests are not available do to level)



Figured it out, i hadnt started HB since yesterday so the pullback message was prolly from yesterday.


BUT.... Just so you know the supposed stable version is Swicthing level 62 toons to nagrand to quest as horde.

 

delete

 

Bot attempts do to buy/sell with Sparik when I am unfriendly with kurenai. Also, I am level 68, no idea why the bot goes back to nagrand to quests...

 

Hi again, Mr_Xm2,

I've captured your first issue to Known Bugs List: Cata 80-85. It looks like that quest may need to be reworked to address it satisfactorily.

For your second issue...
In v2831, we've disabled the "Pull" behavior after the quest completes. We re-enable it after the quest has been turned in.

For the third issue...
Something is interrupting the use of the Twilight Pick on the Lodestone.

[22:25:55.297 D] [InteractWith-v719(debug)] Attempting use of 'Pioche du Cr?puscule' on 'Magn?tite du Sombre murmure'
[22:25:55.297 D] [Lua.Events] Attached to event UNIT_SPELLCAST_FAILED with handler HandleInterrupted
[22:25:55.297 D] [Lua.Events] Attached to event UNIT_SPELLCAST_INTERRUPTED with handler HandleInterrupted​

The log is not providing clues as to why this is happening. So, we'll have to get a toon to see for ourselves. I've also captured this issue to Known Bugs List: Cata 80-85

cheers & thanks for the reports,
chinajade


[size=-2]Ref: Mr_Xm2's problem reports w/logs[/size]

 

Hi, LowKey, and thanks for the log.

[21:46:25.077 D] Goal: Picking Up Quest - Waste Not, Want Not : QuestID - 10055 : To - Dumphry : ID - 21209
...
[21:48:23.443 D] Goal: Goal: Collect Salvaged Metal x 8​

You are doing "Waste Not, Want Not", and there is not a lot of metal available. If someone was just through the area ahead of you, there is even more competition for it.

The profile appears to be functioning correctly. If you click on Honorbuddy's "Info" tab in the main window, it will show you what the task the profile is currently going about.

cheers,
chinajade


[size=-2]Ref: LowKey's original post w/log[/size]

 

Hi, Lannister, and welcome aboard.

As described in Reporting Problems or Seeking Assistance, this is a navigational issue, or a problem with your Honorbuddy installation.

To assist you with this problem, we'll need your full log that captures the issue.

Ref: [Guide] How to attach your log​

cheers,
chinajade

 

Hi, Memelook, and many thanks for the log.

When Honorbuddy makes a vendor run (mail/sell/repair), the profile is not running. You need to report this problem to the Honorbuddy release thread, please. Your log captures the issue well, and this problem needs to get in front of the right people.

cheers,
chinajade


[size=-2]Ref: Memelook's original post w/log[/size]

 

Hi again, 99-LS1-SS,

From your log...

[19:36:09.521 N] Currently Using BotBase : BGBuddy
...
[19:35:13.694 N] Currently Using BotBase : Questing
...
[19:34:31.291 N] Currently Using BotBase : BGBuddy​

Apologies, I assumed you were using Mixed Mode because of this.


Upon further review, I believe this is your problem:

[19:27:51.171 N] Honorbuddy v2.5.8179.697 started.
...
[19:35:13.799 N] Warning: XML Error: Could not parse 'If' body node! - On line 3688
[19:35:13.827 N] Warning: XML Error: Could not parse 'If' body node! - On line 4934
[19:35:13.845 N] Warning: XML Error: Could not parse 'If' body node! - On line 6008​

If you upgrade to the latest Honorbuddy, I believe you will be off-and-away.

cheers,
chinajade

 

Hi, Memelook, and thanks for the log.

Two things:

• Upgrade to the latest version of Honorbuddy
  
  
• Clear your caches. Instructions here:
  HelpDesk: Cache corruption problems

If you are not off-and-away, please post a fresh log, and tell us your new observations.

cheers,
chinajade


[size=-2]Ref: Memelook's original post w/log[/size]

 

The bot doesn't interact with Lump after bringing down his health.

 

Hi, Memelook, and many thanks for the log.

[03:55:44.543 D] [InteractWith-v719(debug)] Interacting with 'Lump'
[03:55:45.780 D] [InteractWith-v719(debug)] Interact with 'Lump' succeeded.
[03:55:46.009 D] [InteractWith-v719(debug)] Mob Lvl 69 Alliance Paladin is not viable for fighting--ignoring SpankMob directive.
[03:55:46.020 D] [Lua.Events] Attached to event UNIT_SPELLCAST_FAILED with handler HandleInterrupted
[03:55:46.030 D] [Lua.Events] Attached to event UNIT_SPELLCAST_INTERRUPTED with handler HandleInterrupted
[03:55:46.030 D] [InteractWith-v719(debug)] Interacting with 'Lump'​

This looks like an Honorbuddy bug to me. For some reason, Honorbuddy is telling us we need to 'clear' a friendly mob near Lump. This is confusing InteractWith as a consequence, since that task cannot be accomplished.

I've seen other reports of such in the forums, and believe that a low-level property managed by Honorbuddy (called Attackable) is broken at the moment. We're at the mercy of a fix for this in HBcore.

You might also want to upgrade your Honorbuddy, and see if that might correct the issue. If it doesn't... as a work-around, please do the quest manually for now.

cheers,
chinajade


[size=-2]Ref: Memelook's original post w/log[/size]

 

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: Memelook's original post w/log[/size]