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

Hi, Weedroid,

If I understand you correctly, this article should help you with the problem:

HelpDesk: Quests are 'green' or 'gray'​

cheers,
chinajade

 

Hi, F299, and thanks for the log!

[06:20:32.194 N] Not in game
[06:20:36.248 D] Downloaded tilemap Azeroth​

It looks like you left the gameworld, but didn't restart Honorbuddy. Please see the Things To Know regarding this very problem.

You are also getting a ton of errors indicating that Honorbuddy can't communicate with the WoWclient:

[06:20:32.193 D] System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 48EFDE7C, Size: 4
...<tons more like this>...​

All bets are off at this point. Its time to restart the WoWclient and Honorbuddy, or possibly reboot your machine.

cheers,
chinajade


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

 

Hi, Tigerlady3012,

Indeed you are spot on, and your toon is trying to sell:

[07:21:23.885 N] Moving to Type: Sell, Name: Lissaf
[07:21:28.199 D] Destination might be indoors. Trying to find a landing location.​

The profile is not running at all during a vendor (sell/repair) run. You will need to make a post into the Support forum for assistance with this problem.

They will probably need screenshots, and exact locations, in addition to the log. This will give them the information they need to forward to the Navigation developers.


cheers,
chinajade



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

 

Hi, Tumbum, and thanks for the report and log!

<sigh> I thought we had this repaired, but guess not. The problem is two different quests go through Gardener Fran at the same time. I've captured this issue back to the Known Bugs List: MoP 85-90.

Hi, Wullie,

Its completely possible I botched the fix. There are two quests, "Hop Hunting" and "Watering Can" that run through Gardener Fran at the same time.

I wrongly qualified the "Hop Hunting" InteractWith with the "watering can" aura, also. That problem is easy to solve. What I don't know is whether or not Gardener Fran provides a 'gossip dialog' as part of the interaction required for "Hop Hunting", or is it a simple 'click to interact'. This should be the only piece of information I need to try another blind fix. You wouldn't happen to remember what kind of interaction she requires for Hop Hunting (gossip or simple click), would you?

cheers,
chinajade


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

 

Hi, Broozah, and thanks for the log file!

Indeed, you've got the classic symptoms of cache corruption:

[07:48:23.394 D] Goal: Picking Up Quest - The Dunes of Silithus : QuestID - 28859 : To - Zen'Aliri : ID - 38269
[07:48:23.402 D] Changed POI to: Type: QuestPickUp
[07:48:23.431 N] [Singular] attention: Pull Distance set to 35 yds by Questing, Plug-in, Profile, or User
[07:48:24.633 D] InteractDebug:363676544
[07:48:24.663 D] Interact Done:363676544
[07:48:27.089 D] InteractDebug:363676544
[07:48:27.121 D] Interact Done:363676544
[07:48:31.183 D] InteractDebug:363676544
[07:48:31.216 D] Interact Done:363676544
[07:48:35.403 D] InteractDebug:363676544
[07:48:35.435 D] Interact Done:363676544
...​

Whether it is the cache or not, this is not a profile issue. The profile is issuing the correct directives given the current quest state that Honorbuddy is presenting to the profile. There is nothing further the profile can do in this regard.

My suggestion would be to try to clear the cache one more time by carefully following the instructions here:

HelpDesk: Cache corruption problems​

If that fails, then try doing a clean Honorbuddy installation:

HelpDesk: "Clean installing" Honorbuddy​

If still no joy, you need to seek more help in the Support forum, as this is not a profile issue.

cheers,
chinajade


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

 

Hi, Sucbich, and thank you for the log.

Alas, the profile is not running at all while you are dead. Those actions are solely Honorbuddy's. I saw where Singular made a small repair to address this issue. However, there is also an Honorbuddy contribution to the problem.

You will need to report this issue to the Support forum, as this issue has nothing to do with the profile pack.

cheers,
chinajade


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

 

Hi, Wullie,

Another spectacular analysis. I've incorporated your findings into v2767.

However, I'm still of the opinion that Broozah's problem is probably cache-related.

cheers,
chinajade


[size=-2]Ref: Wullie's analysis[/size]

 

Hi, Wullie,

These changes have been folded into v2768. I left the coordinates off the Alliance version, so hope that Honorbuddy passes close enough by to find that NPC. If not, we'll fix it up again later.

cheers & many thanks!
chinajade


[size=-2]Ref: Wullie's problem report & fix[/size]

 

Hi, Genzzz,

Absolutely, this thread is for reporting bugs against Kick's 1-90 profile pack. If you need to report a bug against something else, you should post to the appropriate thread or forum. This information may help you figure it out, if you're not certain: Reporting Problems or Seeking Assistance

cheers,
chinajade

 

Hi, Baaatzi,

The problem isn't the profile—the profile will run fine on any locale-specific version of Honorbuddy. The problem is that Honorbuddy DE does not ship with a QuestBot to execute the profile. You can find more information here:

Honorbuddy Deutsche Version - Pressemitteilung​

cheers,
chinajade

 

Hi, Odarn,

The profile pack will not grind unless your level isn't sufficient to continue. It sounds like you might have cache corruption issues, but without a log, we will be unable to assist you with this.

cheers,
chinajade

 

Hi, Mattikins,

If you need assistance, we will need to see the full log attached that captures the issue, please.

Ref: Reporting Problems or Seeking Assistance​

cheers,
chinajade

 

Hi, Slaske255,

We are unable to provide any assistance without a full log file that captures the issue:

Reporting Problems or Seeking Assistance​

If you read that article, you will also understand that 'stuck' issues are not caused by the profile, and there is absolutely nothing the profile can do to help in this regard.

cheers,
chinajade

 

Hi, Wullie,

Traipsing through combat areas is always a problem. The profile has little control of the Combat Routine's pet management. I made similar changes, but not the same as yours.

First, I swapped the PullDistance manipulation with DisableBehavior/EnableBehavior calls. This should completely disable the combat routine (including pet) until we arrive at our destination.

Second, I omitted the <While Condition="Me.Combat"> loop. The profile does not run at all when the toon is in combat, so this should've been a no-op in your testing. If you observed something different, please do tell, and I'm dying to know how it could've possibly worked.

The changes I made are in v2769. If you disagree with the changes, please sing out.

cheers,
chinajade


[size=-2]Ref: Wullie's problem report and recommended repair[/size]

 

Hi, Wullie,

You're probably going to shoot me, because I'm making modifications to your wonderfully tested repairs. Alas, I try to simplify for future maintenance whenever possible. This is the code I went with:

<If Condition="HasQuest(30715) &amp;&amp; !IsQuestCompleted(30715)">

<CustomBehavior File="InteractWith" QuestId="30715" QuestObjectiveIndex="1" MobId="61808"

PreInteractMountStrategy="DismountOrCancelShapeshift"
X="3112.531" Y="2939.607" Z="496.6286" />​

<CustomBehavior File="InteractWith" QuestId="30715" QuestObjectiveIndex="2" MobId="61806"

PreInteractMountStrategy="DismountOrCancelShapeshift"
X="3010.851" Y="2951.922" Z="419.3805" />​

<CustomBehavior File="InteractWith" QuestId="30715" QuestObjectiveIndex="3" MobId="61810"

PreInteractMountStrategy="DismountOrCancelShapeshift"
X="2929.898" Y="2963.946" Z="409.8496" />​

</If>​

The changes are in on v2770, and as always, are up for discussion if you strongly disagree about something.

cheers and many thanks again!
chinajade



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

 

Hi again, Wullie!

We made the coordinate repairs you called out. We also stripped away all the unnecessary looping logic, and substituted Disable/EnableBehavior for the previous manipulation of PullDistance. In v2771, the fragment now looks like this:

<If Condition="HasQuest(30890) &amp;&amp; !IsQuestCompleted(30890)">

<DisableBehavior Name="Combat" />
<CustomBehavior File="InteractWith" QuestId="30890" QuestObjectiveIndex="4"

MobId="61397" GossipOptions="1" WaitTime="1000"
X="1105.988" Y="2541.264" Z="320.4983" />​

<CustomBehavior File="InteractWith" QuestId="30890" QuestObjectiveIndex="3"

MobId="61396" GossipOptions="1" WaitTime="1000"
X="1129.226" Y="2339.38" Z="316.7636" />​

<CustomBehavior File="InteractWith" QuestId="30890" QuestObjectiveIndex="2"

MobId="61395" GossipOptions="1" WaitTime="1000"
IgnoreMobsInBlackspots="false" X="1258.207" Y="2411.045" Z="334.2922" />​

<CustomBehavior File="InteractWith" QuestId="30890" QuestObjectiveIndex="1"

MobId="61378" GossipOptions="1" WaitTime="1000"
X="1337.38" Y="2357.22" Z="332.73" />​

<EnableBehavior Name="Combat" />​

</If>​

cheers, and many thanks again!
chinajade


[size=-2]Ref: Wullie's problem report and repair[/size]

 

Hi, R?kwon,

VERY nice description of the problem! But, as Wullie points out, we really need a log to diagnose problems like these.

Ref: [Guide] How to attach your log​

I'll take a shot at two possibilities.

• First, your cache may have become corrupt. This article should help you eliminate that possibility:
  
  HelpDesk: Cache corruption problems​
  
  
• Second, perhaps the stop/starting of Honorbuddy had you skip over content critical for acquiring the necessary Rep.
  I believe this is very likely. If this is the case, then you need to modify the profile such that IgnoreCheckpoints="true". This article should help you achieve that goal:
  
  HelpDesk: Questing profiles and the Loremaster achievement​

If neither of these have you on your way, please show us a log, and tell us what you are currently observing.

cheers,
chinajade


[size=-2]Ref: R?kwon's original post w/log
Ref: Wullie's response[/size]

 

Hi china i made a thread about kicks with logs etc, but i forgot that u have this thread here since i didnt bot for ages. Could you please be so kind and check my thread?
Sven.

 

Hi, thanks for the response.

However, the profile *is* running *while* he's in combat which is exactly the problem im trying to describe.

I happens quite frequently with my Demo Lock using Singular.

I think I've done a bad job explaining this one in my first post, but fighting mobs on the way isn't the issue here, it's that it tries and fails to open the door *while* in combat still.


Any ideas? I can grab a log next time it happens if you like?

 

Afternoon

Townlong Steps profile.

Line 1153 (ish)

Code:

				<CustomBehavior File="SlayTheFools" QuestId="30979" MobId="62270" CollectionDistance="200" X="1284.1" Y="3945.744" Z="70.2165" />

Pending the update to the actual SlayTheFools behavior itself, we need a similar update to the last time, to dismount first, or else it just sits there.

Code:

				<CustomBehavior File="ForcedDismount" />
				<CustomBehavior File="SlayTheFools" QuestId="30979" MobId="62270" CollectionDistance="200" X="1284.1" Y="3945.744" Z="70.2165" />

Does the trick. Tested and working.

Hope this helps.