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

[chinajade]

Hi, I'm questing with the wotlk profile (svn update) and my bot try to end all quest in the borean tundra zone. I had found a post in past who showed how to turn off chain quest or something like that ? but I can't put my hand back on it now... could you please help me !?

Hi, Weedroid,

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

[post=1105561]HelpDesk: Quests are 'green' or 'gray'[/post]​

cheers,
chinajade

 

[chinajade]

View attachment 105407
Bot thought it would be cute to go to hyjal during twilight highlands questing profile.

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 [post=1259961]Things To Know[/post] 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: [post=1282139]F299's original post w/log[/post][/size]

 

[chinajade]

Hi, I have a problem with questing in Terrokar Forest.
The bot fly to Shattrath, mount, dismount, mount, fly against walls, try to sell ever and ever and not go to Terrokar

View attachment 105498
View attachment 105499
View attachment 105500

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

 

[chinajade]

Quest: Gardener Farm and the Watering Can

Toon just stay infront of the NPC after interact with him to start this event. Doesnt start to run to the places and use the Watercan.

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 [post=1260135]Known Bugs List: MoP 85-90[/post].

Hi,

Just thought I'd take a look at this one, since I recently submitted a fix for this quest, and confirmed it tested and working, as it worked flawlessly for me, so it got my attention when you reported it not working.

Having a look at your logs, there's nothing that jumps out around the time when it's failing at the quest, however, there seems to be a load of errors early on in the log file, specifically when it appears to be loading some of the "utility" quest behaviors. I'm no expert on this (hopefully chinajade or another dev can cast their more experienced eyes over it), but I would guess that some of the required behaviors for this quest, specifically the UseItemOn CustomAction failed to run correctly due to these earlier errors.
Perhaps a fresh install may help.
I've another toon who'll be through here in next few weeks who I can test again with to be sure.

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

 

[chinajade]

I have a problem where I cannot start questing in Sithilus. When I start HB and load your profile (Sithilus), it takes me to Un'Goro Crate and clicks on an NPC trying to pick up a quest I've already completed.

I followed the steps Tony suggested in http://www.thebuddyforum.com/honorb...125595-honorbuddy-npc-interaction-issues.html which was to clear the cache and disable add-ons however it's still an issue.

The quest that it's trying to pick up is called "The Dunes of Sithilus". I installed Quest Completist and it show's that I've already completed the quest.

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:

[post=1067458]HelpDesk: Cache corruption problems[/post]​

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

[post=1120664]HelpDesk: "Clean installing" Honorbuddy[/post]​

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

 

[chinajade]

Ok so I have the latest SVN Update for Kick's Leveling profiles. But for some reason when I die it does not want to release spirit. Here is a log. Please help!

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 [post=1275887]made a small repair[/post] 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: [post=1283540]Sucubich's original post w/log[/post][/size]

 

[chinajade]

Looking at the wowhead notes for that quest, it appears to be a breadcrumb quests to lead you to Silithus, and there also seem to be some other breadcrumb quests that can lead to this chain from different locations, presumably as there are different areas you can level up in before coming here.

It looks like you've been using a different profile pack before switching to Kicks, and although this is generally supported, you should be prepared for anomolies like this. You may have picked up the other breadcrumb quests from different locations, or jumped ahead and done the rest of the chain.

In the first instance, check if you have either of the following in your log, as they will prevent you picking up the quest in Un'Goro:

Warchief's Command: Silithus! - Quest - World of Warcraft
The Sands of Silithus - Quest - World of Warcraft

If you have either in your log, then abandon them, hopefully that sorts it. Otherwise, I suspect you've already completed the quests following this in the chain, and that is the reason you can't pick it up.

I would recommend the following change to the profile. 1-58 Horde Line 8519 Current:

<PickUp QuestName="The Dunes of Silithus" QuestId="28859" GiverName="Zen'Aliri" GiverId="38269" X="-7461.412" Y="-1528.385" Z="-268.8134" />

Recommended change. Please note this is a blind fix:

<If Condition="!HasQuest(28527) && !HasQuest(28856) && !HasQuest(28528) && !HasQuest(8280) && !IsQuestCompleted(8280)">
<PickUp QuestName="The Dunes of Silithus" QuestId="28859" GiverName="Zen'Aliri" GiverId="38269" X="-7461.412" Y="-1528.385" Z="-268.8134" />
</If>

This will ensure that we don't have any of the other breadcrumb quests, and that we've not completed the followup, before trying to obtain this quest. To completely tidy this up, we should probably also change the hand-in logic to check and try to hand in the other quests if we have them, however worse case scenario the user is sees the bot stopped next to a NPC with a quest to hand in so it's an easy and obvious remedy for them.

Hope this helps.

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: [post=1283847]Wullie's analysis[/post][/size]

 

[chinajade]

Questing in Kun-Lai/VoEB. Level 90 Horde.
Kun-Lai profile.
Guess with all the changes in 5.4 there were bound to be a few quests get borked.
A Witness to History - Quest - World of Warcraft
This quest is currently set to complete using the following (Line 2788):

<TurnIn QuestName="A Witness to History" QuestId="31511" TurnInName="Zhi the Harmonious" TurnInId="59905" X="1215.917" Y="1041.448" Z="425.9666" />

Zhi the Harmonious - NPC - World of Warcraft
Zhi the Harmonious is no longer in game as of 5.4, and causes the TurnIn behavior to go a bit crazy seems to think it's stuck where the NPC should be, and just endlessly runs the stuck logic causing it to walk back and forth around where the NPC should be (Doesn't actually seem to be a mesh issue, rather a bug cause of the NPC not being there - perhaps worth further investigation).
Madam Vee Luo - NPC - World of Warcraft
Madam Vee Luo in Shrine of Two Moons (For Horde anyway) now completes this quest.
Please update that line to the following:

<TurnIn QuestName="A Witness to History" QuestId="31511" TurnInName="Madam Vee Luo" TurnInId="62996" X="1700.95" Y="893.58" Z="470.98" />

Please note that the Alliance version of this quest (A Witness to History - Quest - World of Warcraft) will also need changed, and is now handed in at (Matron Vi Vinh - NPC - World of Warcraft). I don't have any Alliance toons to test with so can't give coords, sorry.
The Horde fix is tested and working
I suspect that there may be a few other issues around this area because of the changes, so will clear up what I can as I go.

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: [post=1284432]Wullie's problem report & fix[/post][/size]

 

[chinajade]

Hi, can we repport bug we see here ?

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: [post=1259963]Reporting Problems or Seeking Assistance[/post]

cheers,
chinajade

 

[chinajade]

is there any possibility to use the profile with the current german version of honorbuddy?
i get the message that the questing behaviors can not be found...

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

 

[chinajade]

please get rid of the grind parts, they are really not necessary! I am always wondering what the ... my toon is doing running around like a fool instead of turning in quests and going on.

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

 

[chinajade]

Alright so I was running your profile for BC and it was working fine until all of a sudden I got the error message "Can not turn in quest A Message to Telaar (ID: 9792) because I don't have it in my quest log! (Or do I: False)
Bot Stopped! Reason: Could not create current in quest bot!"

I deleted the bot cache and the WoW cache. Still keep on getting the same error message when I start it up. Will try a fresh install of honorbuddy.

Edit: I reinstalled Kick's Profiles AND Honorbuddy and I'm still getting the same message " Can not turn in quest A Message to Telaar (ID: 9792) because I don't have it in my quest log! (Or do I:False)"

Hi, Mattikins,

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

Ref: [post=1259963]Reporting Problems or Seeking Assistance[/post]​

cheers,
chinajade

 

[chinajade]

is it normal that there is so many bugs in this profile?
im right now level 69 leveling in borean thundra. the bot by now got stuck 4 times. one time in a tent, flying constantly forward. now 2 times the same place, trying to kill a mob through a wall by landing on this tent kinda thing. and at last it just got stuck by a stone or something like that.

EDIT: dont ask for a log... -.- the log says nothing about the character got stuck in these places

Hi, Slaske255,

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

[post=1259963]Reporting Problems or Seeking Assistance[/post]​

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

 

[chinajade]

This next one I was hoping for a little guidance on...
It's long (at least for last 6 months) been the case that the InteractWith type CustomBehaviours *dont* complete when the bot is still in combat (at least a lot of the time anyway - not sure exactly when it does and when it doesn't). I'm presuming everyone is aware of this. It can cause issues where it'll run to items to try and interact with them and fail and blacklist them.
Perhaps this is by design, perhaps it's a bug, I'm not totally sure.
Depending on the character and the combat routine this can be more or less noticeable when questing. Those with pets probably notice this a lot more.
For instance I'm using Singular with a Demo Warlock. Am not completely sure how the interaction happens between the questing profile and the combat routine, but I'd guess there must be some sort of "priority" in there, and once a threshold is reached the CR allows the bot to continue doing questing stuff, while the pet fights the mobs. This is a really great idea, as it's exactly how a real player would play, and I've got to say it gets the balance right in most cases - eg the damage to do before it lets the pet "deal" with the mob(s) and continues doing it's next quest related thing.
However, where it falls down a lot of the time is that it'll run around trying to interact with items and failing because it's in combat. It seems to often blacklist the items and run off to the next, which in fact causes the questing to take longer than if I had just waited till combat completed before doing anything.
Sometimes this can be a complete AFK breaker. For instance in Kun-Lai profile, Line 2806:

<If Condition="HasQuest(31453) && IsQuestCompleted(31453)"> <!-- H - In from right side -->
				<CustomBehavior File="UserSettings" PullDistance="1" />
				<RunTo X="1864.344" Y="2018.345" Z="454.1613" />
				<CustomBehavior File="WaitTimer" WaitTime="2000" GoalText="Waiting for agro to clear {TimeRemaining}" />
				<RunTo X="1864.344" Y="2018.345" Z="454.1613" />
				<CustomBehavior File="InteractWith" MobId="215382" ObjectType="GameObject" Range="8" WaitTime="0" X="1864.515" Y="2020.56" Z="455.668" />
				<RunTo X="1866.205" Y="2055.865" Z="455.6911" />
		<TurnIn QuestName="The Shado-Pan" QuestId="31453" TurnInName="Shado-Master Chong" TurnInId="60161" X="1866.205" Y="2055.865" Z="455.6911" />
				<CustomBehavior File="UserSettings" PullDistance="15" />
			</If>

Now, in this case the InteractWith is to open a door. We're just ran through a heavily mob populated area, and chances are we're in combat. I certainly was. This means the door doesn't get opened and the bot just stands there. Of course, a stop-start would remedy it as the InteractWith would be called again and most likely this time we're out of combat.
Unless there is an up and coming fix to the in-combat issue then I'd recommend the following changes (Also done the Alliance counterpart here):

<If Condition="HasQuest(31453) && IsQuestCompleted(31453)"> <!-- H - In from right side -->
				<CustomBehavior File="UserSettings" PullDistance="1" />
				<RunTo X="1864.344" Y="2018.345" Z="454.1613" />
				<CustomBehavior File="WaitTimer" WaitTime="2000" GoalText="Waiting for agro to clear {TimeRemaining}" />
				<RunTo X="1864.344" Y="2018.345" Z="454.1613" />
				<While Condition="Me.Combat">
					<CustomBehavior File="WaitTimer" WaitTime="2000" GoalText="Waiting for combat to clear {TimeRemaining}" />
				</While>
				<CustomBehavior File="InteractWith" MobId="215382" ObjectType="GameObject" Range="8" WaitTime="0" X="1864.515" Y="2020.56" Z="455.668" />
				<RunTo X="1866.205" Y="2055.865" Z="455.6911" />
		<TurnIn QuestName="The Shado-Pan" QuestId="31453" TurnInName="Shado-Master Chong" TurnInId="60161" X="1866.205" Y="2055.865" Z="455.6911" />
				<CustomBehavior File="UserSettings" PullDistance="15" />
			</If>
			<If Condition="HasQuest(31455) && IsQuestCompleted(31455)"> <!-- A - In from right side -->
				<CustomBehavior File="UserSettings" PullDistance="1" />
				<RunTo X="1864.344" Y="2018.345" Z="454.1613" />
				<CustomBehavior File="WaitTimer" WaitTime="2000" GoalText="Waiting for agro to clear {TimeRemaining}" />
				<RunTo X="1864.344" Y="2018.345" Z="454.1613" />
				<While Condition="Me.Combat">
					<CustomBehavior File="WaitTimer" WaitTime="2000" GoalText="Waiting for combat to clear {TimeRemaining}" />
				</While>
				<CustomBehavior File="InteractWith" MobId="215382" ObjectType="GameObject" Range="8" WaitTime="0" X="1864.515" Y="2020.56" Z="455.668" />
				<RunTo X="1866.205" Y="2055.865" Z="455.6911" />
		<TurnIn QuestName="The Shado-Pan" QuestId="31455" TurnInName="Shado-Master Chong" TurnInId="60161" X="1866.205" Y="2055.865" Z="455.6911" />
				<CustomBehavior File="UserSettings" PullDistance="15" />
			</If>

For this particular one I flew back to then other side of the mob heavy area, and kicked it off again, to ensure it was tested when in combat. Worked perfectly.
Let me know your thoughts as to whether individual fixes like this are the way you'd like to address this or not.

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: [post=1284463]Wullie's problem report and recommended repair[/post][/size]

 

[chinajade]

Questing in Kun-Lai. Level 90 Horde.

Quest: A Line Unbroken - Quest - World of Warcraft

Gets stuck in this loop *after* doing the initial interactwith, which causes the mob to disappear. The objective shows as completed, so I suspect that it's simply not registered the objective as completed quickly enough, and then got stuck in the loop.

			 <While Condition="!IsObjectiveComplete(1, 30715)">
				<RunTo X="3112.531" Y="2939.607" Z="496.6286" />
				<CustomBehavior File="ForcedDismount" />
				<CustomBehavior File="InteractWith" MobId="61808" X="3112.531" Y="2939.607" Z="496.6286" />
			 </While>

I've added a WaitTime and since it's in a loop anyway, set "WaitForNpcs" to false, to prevent it getting stuck in a 2nd "hit" of this InteractWith *after* the first one worked.

Please change to:

			 <While Condition="!IsObjectiveComplete(1, 30715)">
				<RunTo X="3112.531" Y="2939.607" Z="496.6286" />
				<CustomBehavior File="ForcedDismount" />
				<CustomBehavior File="InteractWith" MobId="61808" X="3112.531" Y="2939.607" Z="496.6286" WaitForNpcs="False" WaitTime="2000" />
			 </While>

Thanks

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: [post=1284478]Wullie's problem report w/log[/post][/size]

 

[chinajade]

Questing with Townlong Steps profile. Level 90 Horde.

Line 965:
It should be changed to the following:

			  <While Condition="!IsObjectiveComplete(1, 30890)">
				<RunTo X="1337.38" Y="2357.22" Z="332.73" />
				<CustomBehavior File="InteractWith" MobId="61378" GossipOptions="1" WaitTime="1000" X="1337.38" Y="2357.22" Z="332.73" />
				<CustomBehavior File="UserSettings" PullDistance="25" />
			  </While>

Tested, confirmed to be working.

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: [post=1285274]Wullie's problem report and repair[/post][/size]

 

[chinajade]

Hi, first of all, thank for getting my toon until level 66 pretty much without any troubles. I have encountered the problem I'll explain furhter a few times while leveling this toon, but I usually got around it by completing a few quest by myself or something like that, then I came here and read a bit of the thread and I figured out that reporting the bug/asking for help is the best thing to do.

After the character dinged 66 the bot decided to go to Nagrand and pickup quests at the maghar outpost in Garadar. It picked The Impotent Leader, but then I stopped the bot since I figured out he had 3 completed quests from Terrokar he didn't turn in. I turned them in manually, put the toon back to Garadar and started honorbuddy again.
The bot then decided he had to talk to Warden Bullrok to pick up Proving Your Strength. The problem is that the NPC is Unfriendly, as all the Mag'har are at first!

I hope that the problem was not me doing the turn in manually, but I figured out he was going to skip them because he dinged 66 and Terrokar was his zone no more! I thought "damn! those exp can help, why skip it?!". Also, as I mentioned earlier, this kind of problem (looking for a quest pick up from an NPC which had no quests) has happened at least a couple of times during the levelling and without my "help".

What do I have to do now anyway?

Hi Raekwon,
I've had a brief look over the profile, but without a log it's difficult to see what's going on.
As soon as we enter Nagrand (eg when hitting level 66), we hit the following section of the profile (Line 4541):

<!-- Grind to Neutral -->
            <If Condition="Me.GetReputationLevelWith(941) < Styx.WoWUnitReaction.Neutral" >
                <!-- add the 9407 questline here -->

                <CustomBehavior File="Message" Text="Getting to Neutral with Mag'har - do not interfere!" LogColor="Orange" />
.................
.................

As you can see, we're checking against the reputation with faction 941 (The Mag'har - Faction - World of Warcraft), and if we're not already Neutral should go and do a bunch of quests to make sure we are.
As per the first page of this thread, specifically the section about reporting problems (http://www.thebuddyforum.com/honorbuddy-forum/submitted-profiles/131188-kicks-1-90-mega-profile-pack.html#post1259963), please provide a log so people can see what's going on and try and help.
Unfortunately, without the log I can only start to guess what's happened which isn't very helpful to anyone, and there are a number of things that have the potential to cause this, both profile related, and user related

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: [post=378165][Guide] How to attach your log[/post]​

I'll take a shot at two possibilities.

• First, your cache may have become corrupt. This article should help you eliminate that possibility:
  
  [post=1067458]HelpDesk: Cache corruption problems[/post]​
  
  
• 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:
  
  [post=1067958]HelpDesk: Questing profiles and the Loremaster achievement[/post]​

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: [post=1285425]R?kwon's original post w/log[/post]
Ref: [post=1285540]Wullie's response[/post][/size]

 

[Svenstar123]

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.

 

[Wullie]

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: [post=1284463]Wullie's problem report and recommended repair[/post][/size]

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?

 

[Wullie]

Afternoon

Townlong Steps profile.

Line 1153 (ish)

				<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.

				<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.