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

Thanks once again, MaxMuster.

We've done a couple of things with your information.

1. Apply your recommended repair to both the Alliance and the Horde profiles.
   The changes should be available in v3038.
   
   
2. Submit bug report HB-314 in the hopes that Flightor and the stuck handler could be improved from the information provided by this testbed.

cheers & thanks again!
chinajade


[size=-2]Ref: MaxMuster's problem report w/recommended repair[/size]

 

Hi, MaxMuster,

Your recommended repairs have been folded into v3039.

Thanks again!
chinajade


[size=-2]Ref: MaxMuster's problem report w/recommended repair[/size]

 

<waves at MaxMuster>,

Your coordinate refinements have been folded into v3040.

cheer & thanks!
chinajade


[size=-2]Ref: MaxMuster's problem report w/recommended refinements[/size]

 

Hi, Daarno,

Its not as simple as you describe, but there are techniques we can employ to solve this problem. Alas, we don't believe it is the smart thing to do.

Since Colderra is uneven terrain, it looks too bot-like to use a ground mount in this area. Agreed, that getting eaten by the flying wyrms is not much of an improvement, but we believe it is the lesser of the two evils.

If you feel strongly about the issue, please submit an improvement request to the Feedback for Honorbuddy Improvements thread, and ask for Flightor (the flying navigator) to actively avoid such dangerous flying mobs.

cheers,
chinajade

 

Hi, MaxMuster, and thanks for the report!

We reworked all the quests dealing with Archimage Berinand (in the Colderra house). The changes have been folded into v3041.

cheers,
chinajade


[size=-2]Ref: MaxMuster's problem report and recommended repairs[/size]

 

Hi again, MaxMuster.

Indeed, the two behaviors were redundant. The second one probably was added to work around a temporary bug in InteractWith, and was never removed when the InteractWith was repaired. We deleted the redundant CombatUseItemOnV2 call. Nice watching!

Your improved hotspot list has been folded into v3042.

Not surprising—its simply amazing how quick profiles will 'bit rot' as changes get made to Honorbuddy.
It wasn't that long ago that Hawker reworked it, and it was smooth as glass for a couple of months.

Aye, we are actively working through the profiles trying to make changes like you describe. Some have already been made, and others are coming. We're working off a very large TODO list.

And once again, THANK you for the many nicely wrapped improvements you're always tossing our way.

cheers,
chinajade


[size=-2]Ref: MaxMuster's problem report w/recommended repairs[/size]

 

Hi, Dylan1211,

Honorbuddy itself makes most of these decisions. Without a full log that demonstrates the issue, we've no real way to help you.

Please see the guide for Reporting Problems or Seeking Assistance.

cheers,
chinajade

 

Hi, Daarno, and thank you for the log.

[02:53:24.198 N] [Singular] We have no food/drink. Waiting to recover our health/mana back ​

The reason its taking so long is a configuration error, and not Honorbuddy. Configure your toon to buy some food/water.

Ref: Things To Know​

cheers,
chinajade


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

 

Hi, SiFi2010, and thanks for the log.

Somehow, your toon's quest state has become damaged. Did you do the alternative Of Traitors and Treason - Quest - World of Warcraft (from Howling Fjord) manually, perchance?

This article will help resolve most issues related to this problem...

HelpDesk: Quest giver is not offering expected quest​

cheers,
chinajade


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

 

Hi, Cyanide, and many thanks for the log.

// The Mech Control Scrambler is being used correctly...
[18:55:13.757 D] Goal: CombatUseItemOn-v1100: ""Core Access Codes" (http://wowhead.com/quest=27777)"
[Ref: "[Fly][N - Quest] Uldum 83-85 [Kick] ($Rev: 3013 $)" @line 1102]
...
[18:55:20.247 D] Activity: Using item
...
// Toon kills the mob and loots the mob...
[18:55:43.374 N] [Singular] Bot TargetList is empty, no targets available
[18:55:43.374 N] [Singular] EnsureTarget: no valid target set -- skipping spell priority
[18:55:44.577 D] Changed POI to: Type: Loot, Name: Twizzleflux the Insane
...
// WoWclient is not giving credit for the needed loot...

"Core Access Codes"(Core Access Codes - Quest - World of Warcraft) incomplete
Core Access Codes: 0/1 (type: CollectItem) ​

This looks like a WoWclient glitch to me. You might try killing the WoWclient and restarting. It would also be a good idea to clear the caches again while the WoWclient is closed:

HelpDesk: Cache corruption problems​

cheers,
chinajade


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

 

Hi, Myrgy,

Absolutely no way to assist you with problems like this, unless you attach the full log that captures the issue. Please see the guide for Reporting Problems or Seeking Assistance.

cheers,
chinajade

 

Sweet, another useless quest override bites the dust!

Changes have been folded into v3043.

Many thanks again, MaxMuster!

cheers,
chinajade


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

 

Hi, Kaelhoel,

From the description, doesn't sound like a profile problem. Please see the guide for Reporting Problems or Seeking Assistance.

cheers,
chinajade

 

Hi, Daarno, and many thanks for the log.

We do not support questing with Beta versions of Honorbuddy. If you have a problem, please submit logs from Released versions of Honorbuddy only. Please see the following article: Things To Know.

cheers,
chinajade

 

Hi, Nixonyx,

And, welcome aboard!

cheers,
chinajade

 

Hi, MrLolPlz, and many thanks for the log.

This is classic cache corruption. This article should help you sort the problem...

HelpDesk: Cache corruption problems​

cheers,
chinajade


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

 

Profile: [H - Quest] 12-58 K-EK [Kick]

For the Quests in Tanaris and Silithus we should set the TargetingDistance higher, to 100 because the mobs are most to far away from the bot (when using TargetingDistance 40) and then he ignore it.

Replace:

Code:

        <CustomBehavior File="Message" Text="Compiling Tanaris Quests" LogColor="Green" />

With:

Code:

        <CustomBehavior File="Message" Text="Compiling Tanaris Quests" LogColor="Green" />
        <TargetingDistance Value="100" />

And Replace:

Code:

        <TurnIn QuestName="Returning a Favor" QuestId="24905" TurnInName="Megs Dreadshredder" TurnInId="38849" />

With:

Code:

        <TurnIn QuestName="Returning a Favor" QuestId="24905" TurnInName="Megs Dreadshredder" TurnInId="38849" />

        <TargetingDistance Value="40" />

So we Set the TargetDistance for Tanaris to 100, and back when all Tanaris Quests Done.


And make the same for Silithus:

Replace:

Code:

        <CustomBehavior File="Message" Text="Compiling Silithus Quests" LogColor="Green" />

With:

Code:

        <CustomBehavior File="Message" Text="Compiling Silithus Quests" LogColor="Green" />
        <TargetingDistance Value="100" />

And Replace:

Code:

        <CustomBehavior File="Message" Text="All done in Silithus." LogColor="Yellow" />

With:

Code:

        <TargetingDistance Value="40" />
        <CustomBehavior File="Message" Text="All done in Silithus." LogColor="Yellow" />

And maybe we should then set for both Areas the KillBetweenHotspots from True, to False. Otherwise we maybe got problems with targeting to much mobs between hotspots (move to a hotspot or move to pickup/turn in a quest).

Tested (for Silithus) and works a lot smoother.


P.S. The best solution is to let KillBetweenHotspots on True and set the TargetDistance for needed quest (in Tanaris and Silithus) individuell, but thats need to much time for me at the moment to check for what quests we should do this. So my Solution is a Fast-Dirty Solution ;-)

In Tanaris we need this for Quests in this Area http://i.epvpimg.com/58Duc.jpg for Example when Grinding crocodiles and hyenas for a quest.



[EDITED 6-Jan-2014 by chinajade]: Hi, MuxMaster! I'm going to hold on to this one for a little while. The Alliance-side 1-58 profiles have been reworked with regard to things like this, and the Horde side are next. We'll address these issues with that rework.

 

Profile: [Fly][H - Quest] LK 68-80 [Kick]
Quest: The Damaged Journal - Quest - World of Warcraft
Descirption: Improvements

Now it makes:
1) Check if we have 8 Paper. When not use the FlyTo, ForceDismoutn and the Objective.
2) When we have 8 paper and can craft the item. FlyTo the Base Camp and Mount Down.
3) Use a While Loop to Craft the Item, bceause sometimes it not works on the first time.

Replace:

Code:

                <CustomBehavior File="FlyTo" X="4720.599" Y="-4466.088" Z="194.6105" />
                <CustomBehavior File="ForcedDismount" />
                <Objective QuestName="The Damaged Journal" QuestId="12026" Type="CollectItem" CollectCount="8"
                           ItemId="35737" />

                <CustomBehavior File="Misc\RunLua" WaitTime="1000" Lua="UseItemByName(35739)" />
                <CustomBehavior File="WaitTimer" WaitTime="5500" />

With:

Code:

                <If Condition="GetItemCount(35737) &lt; 8">
                  <CustomBehavior File="FlyTo" X="4720.599" Y="-4466.088" Z="194.6105" />
                  <CustomBehavior File="ForcedDismount" />
                  <Objective QuestName="The Damaged Journal" QuestId="12026" Type="CollectItem" CollectCount="8"
                             ItemId="35737" />
                </If>
                <If Condition="GetItemCount(35737) &gt;= 8">
                  <CustomBehavior File="FlyTo" X="3851.104" Y="-4523.887" Z="209.4062" />
                  <CustomBehavior File="ForcedDismount" />
                </If>
                <While Condition="(GetItemCount(35737) &gt;= 8) &amp;&amp; !IsQuestCompleted(12026)">
                    <CustomBehavior File="Misc\RunLua" WaitTime="1000" Lua="UseItemByName(35739)" />
                    <CustomBehavior File="WaitTimer" WaitTime="5500" />
                </While>

 

How can i make it do all 58-70 quests when im lvl 90 ? I've done 1 or 2 started quests in hellfire and ive increased the maxlvl etc in the profile. All its doing is going back to org, going through the blasted lands portal-> TBC portal then going shatt->org->all over again

 

Replace:

Code:

<QuestOrder IgnoreCheckpoints="False >

With:

Code:

<QuestOrder IgnoreCheckpoints="True" >