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

Hi, Zeven, and thanks for the log.

This looks like a user error:

[07:01:26.277 D] [InteractWith-v1538(debug)] Interact with 'Rally Zapnabber' succeeded.
[07:01:26.343 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[07:01:26.343 D] Removed hook [Combat_Only] 41971558-badc-47fe-853c-1bbbcd8fe6a8
[07:01:26.343 D] Removed hook [Death_Main] 56936740-8997-4296-8513-755598992d6e
[07:01:26.357 D] [InteractWith-v1538(debug)] Behavior completed in 2s
[07:01:26.357 D] Goal: Nothing
[07:01:26.357 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[07:01:26.357 D] Goal: WaitTimer-v1581: In Progress (no associated quest)
[Ref: "[N-Quest]Blade's Edge Mountains(67-68)[Cava] $Rev: 278 $" @line 1413]
[07:01:26.357 D] Goal: WaitTimer-v1581: In Progress (no associated quest)
Waiting for 30s
[Ref: "[N-Quest]Blade's Edge Mountains(67-68)[Cava] $Rev: 278 $" @line 1413]
[07:01:26.666 D] Activity: Wait time remaining... 29s of 30s.
[07:01:27.669 D] Activity: Wait time remaining... 28s of 30s.
[07:01:28.671 D] Activity: Wait time remaining... 27s of 30s.
[07:01:29.671 D] Activity: Wait time remaining... 26s of 30s.
[07:01:30.671 D] Activity: Wait time remaining... 25s of 30s.
[07:01:31.670 D] Activity: Wait time remaining... 24s of 30s.
[07:01:32.378 D] Activity: Wait time remaining... 23s of 30s.
[07:01:33.407 D] Activity: Wait time remaining... 22s of 30s.
[07:01:34.389 D] Activity: Wait time remaining... 21s of 30s.
[07:01:35.409 D] Activity: Wait time remaining... 20s of 30s.
[07:01:36.395 D] Activity: Wait time remaining... 19s of 30s.
[07:01:37.414 D] Activity: Wait time remaining... 18s of 30s.
[07:01:38.397 D] Activity: Wait time remaining... 17s of 30s.
[07:01:39.413 D] Activity: Wait time remaining... 16s of 30s.
[07:01:40.396 D] Activity: Wait time remaining... 15s of 30s.
[07:01:41.411 D] Activity: Wait time remaining... 14s of 30s.
[07:01:42.134 Q] Bot stopping! Reason: Main window is closing​

This shows the WoWclient was closed while the profile was waiting for the quest to complete. This is obviously not a profile problem.

cheers,
chinajade


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

 

Hi, Fliegsdingsbums,

As stated in Reporting Problems or Seeking Assistance, "compile errors" are not a problem with the profile, but your Honorbuddy installation.

Please follow the instructions in this article for getting the problem cleaned up:

Honorbuddy:HelpDesk:"Clean installing" Honorbuddy​

cheers,
chinajade

 

Hi, TreeEskimo,

We have yet to re-flow the Outland profiles for flying earlier. This article provides more information:

HelpDesk: Honorbuddy and flying​

cheers,
chinajade

 

Hi, Ale56man, and thanks for the log.

There is absolutely nothing a profile can do to cause you to disconnect from either the Buddy Auth server, or the WoWserver.

The log doesn't show anything besides you like to press Honorbuddy's "Stop" button a lot.

If the problem persists, please make a new thread in the Support forum with a log that captures the problem (this log does not).

cheers,
chinajade


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

 

Hi, Sealice,

Those mobs that appear to have lootables on them are duplicate quest items. Some quests in WoW continue to drop quest items when you are in a party. The first time you loot the corpse, you will see everything. However, if you close the box and look again at the sparkling corpse, nothing will be shown if you already have the needed quest items. If another party member needs the item, he will be able to see it when the corpse is looted, even though you saw the corpse as 'empty'. Despite this, the corpse will continue to sparkle and confuse users.

This is how WoW works for certain quests, and nothing we can do about it. Honorbuddy is smart enough to know when these situations occur, and not try to reloot corpses with unlootable items on them.

As far as your other issues, we'll need to see a full log attached to your post that captures whatever issue you are having. We need this log to analyze the problem. Without it, we are blind and unable to assist you.

Ref: [Guide] How to attach your log​

cheers,
chinajade

 

Hi, Virus2001, and thanks for the log.

[18:17:42.622 D] Changed POI to: Type: QuestPickUp
[18:17:42.714 N] [Singular] info: Pull Distance set to 35 yds by Questing, Plug-in, Profile, or User
[18:17:42.728 N] I don't want to move to <0, 0, 0>
[18:17:42.748 D] Activity: Waiting for object to appear to pick up quest from
[18:17:42.877 N] I don't want to move to <0, 0, 0>
[18:20:11.571 N] Stopping the bot!​

The profile has issued the correct directive to pick up a quest. However, Honorbuddy is having problems finding the location. This leads us to believe there is either a problem with your cache, or your Honorbuddy installation. Since you are two revs behind in your Honobuddy version, we believe a "clean install" of the latest version will clear the problem:

Ref: Honorbuddy:HelpDesk:"Clean installing" Honorbuddy​

cheers,
chinajade


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

 

Hi, Ale56man,

The profile pack is designed to loot everything. There are no accommodations for 'turning looting off'. If you do so, you will miss quest items, and will go nowhere real fast.

We would have to rewrite the entire pack to do what you desire. That's half-a-million lines of profile code, and isn't going to happen.

cheers,
chinajade

 

Hi, TreeEskimo,

If you need assistance, we will need the full log attached, please. Partial logs are useless.

cheers,
chinajade

 

Hi, Sealice,

As described in Reporting Problems or Seeking Assistance, "stuck" issues are not problems with the profile.

Such things should be reported to the Navigation thread, instead. Please follow the instructions in the first post in that thread if you wish the issue to be resolved.

cheers,
chinajade

 

Hi, Yarbej, welcome aboard, and many thanks for the log.

[19:22:23.529 D] [GoThruPortal-v1581(debug)] Portal Entry Timer Started
[19:22:23.529 D] [GoThruPortal-v1581(debug)] Entering portal via <-11207.61, 1692.406, 23.88796>
[19:22:29.794 N] Not in game
[19:22:33.979 D] (Singular) MapId = 36
[19:22:34.041 D] (Singular) ZoneId = 40
[19:22:34.103 V] (Singular)
[19:22:34.165 D] (Singular) Talents Selected: 1
[19:22:34.227 D] (Singular) --- #1 - Juggernaut
[19:22:34.288 V] (Singular)
[19:22:34.356 D] (Singular) Glyphs Equipped: 0
[19:22:34.418 V] (Singular)
[19:22:34.480 V] (Singular)
[19:22:33.978 N] [Singular] Your Level 16 Human Protection Warrior Build is
[19:22:33.979 N] [Singular] ... running the Questing bot in Moonbrook [5-player Normal]
[19:22:34.103 N] [Singular] ... Dungeon using my SOLO Behaviors
[19:22:34.541 V] (Singular) My Current Dynamic Info
[19:22:34.664 V] (Singular) =======================
[19:22:34.726 D] (Singular) Combat Reach: 1.5000
[19:22:34.787 D] (Singular) Bounding Height: 2.0313
[19:22:34.849 V] (Singular)
[19:22:35.281 D] Downloaded tilemap DeadminesInstance
[19:22:35.528 D] Changed map(s) to DeadminesInstance
[19:22:35.530 N] [GoThruPortal-v1581(warning)] Unable to enter portal within allotted time of 10s

The WoWserver was experiencing heavy lag when you entered the Deadmines portal. Basically, you took more than 12 seconds to zone for something that should have been done in 4 seconds. We allow for a 2.5x factor of safety in the zoning process, and your session exceed this.

The GoThruPortal behavior wanted to go back and 'try again', but it couldn't figure out how. So, it stood still until Honorbuddy's inactivity timer expired, and terminated your session.

This is why you experienced this problem, and should be a one-time issue. Unless, your server always has this problem.

cheers,
chinajade


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

 

Hi, Kontest,

This issue was repaired recently, you just need to update your local copy of the profile pack again.

cheers,
chinajade

 

Hi, Adeal,

This question is answered in the FAQ.

cheers,
chinajade

 

Hi, Velonici, and many thanks for that log!

We see what you describe:

[03:06:28.697 D] Loading Northrend_21_25
[03:06:29.823 N] Moving to Type: QuestTurnIn
[03:06:55.629 N] Stopping the bot!​

The problem actually lies in Honorbuddy's flying navigator, not the profile. As a work-around in v3391, we've disabled flying for the turnin of this quest.

cheers,
chinajade


[size=-2]Ref: Velonici's problem report w/log[/size]

 

Hi, Valtherous, and welcome aboard.

There is one quest where it is a bit thorny since Honorbuddy does not actively avoid mobs that 'walk in'. This quest is Into the Realm of Shadows. The problem is not a profile problem, but one of mob avoidance during combat. There is nothing a profile writer can do about this.

Although this quest is sometimes thorny, we've never seen it not complete, even if a few deaths are involved.

Outside that one quest, the DK starting zone should be smooth as glass. If you are having issues, we'll need to see your full log attached, please.

Ref: [Guide] How to attach your log​

And... you will need to describe the specific problem you are observing.

cheers,
chinajade

 

Hi, Zimmy130, and thanks for those logs!

[13:16:13.675 N] Can not turn in quest The King's Command (ID: 29547) because I don't have it in my quest log!​

The King's Command is an automatically given quest while standing in Stormwind, and you're ready for Panderia. From what you've said, you've already done this quest. As such, it appears that your caches have become corrupt, and this article should help you sort the issue:

HelpDesk: Cache corruption problems​

If you are not off-and-away, please show us another fresh log after the caches have been cleared.

cheers,
chinajade


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

 

Hi, Tdevine21,

We'll be unable to assist you with problems like this, unless you attach the full log that captures the problem.

Ref: [Guide] How to attach your log​

cheers,
chinajade

 

Thanks for all the hundreds of contributions you make to refine them, MaxMuster!

We've folded your new datapoints into the FAQ.

cheers & thanks again!
chinajade

 

Hi, Silencepvper,

There is no way to assist you with problems like this, unless you attach the full log that captures the issue.

Ref: [Guide] How to attach your log​

cheers,
chinajade

 

Hi, Nastypirate, and thanks for the logs and report!

We made a blind fix, and both issues should be correct in v3393. Although for the second issue, we don't understand how you could've gotten up on the bluff (we don't fly you up there), and unable to get back down. This may actually be a navigation issue, not a profile issue.

cheers,
chinajade


[size=-2]Ref: Nastypirate's problem report w/logs[/size]

 

Hi, Nashoune,

This article should answer your question:

HelpDesk: Questing profiles and the Loremaster achievement​

cheers,
chinajade