Hi again.
Questing in Kun Lai Summit. Level 89. Horde.
Bot been running really smooth pretty much AFK since my last post, which is the majority of Kun Lai, so kudos to the team!
I've hit an issue where it's got stuck. My last three characters through here have got stuck in exactly the same spot, and the unstuck routine wasn't running at all.
Specifically we're in Zouchin Village, coming up the northern path to the village, and getting stuck on the woodern fortifications.
Now I know normally these issues should go to the Navigational thread, but please hear me out and don't hit me with the "not-a-profile-issue" stick!
There's a couple of reasons I'm raising it here, rather than the Nav thread:
So, looking at the current profile. Line 2389 onwards:
Now, that first RunTo (4413,807,87) take it to standing just next to the obstacle. The following NoCombatMoveTo takes it on a path right through the wooden fortification, which seemingly isn't meshed.
I would propose another intermediate step, with NoCombatMoveTo going to 4403.85, 812.43, 91.51, which would move it just past the fortification.
So, change as follows:
I considered putting inside the "If" block of the previous quest, but figured that if the user stopped and started after completing the previous quest, it's probably best to run it anyway and get to a "safe" spot.
Let me know your thoughts...
Edit: Tested and working
Edit2: As an afterthought - would small blackspots work for these unmeshed obstacles?
If blackspots would work then here they are:
East 1
4407.13, 1004.90, 95.19 Radius 4
East 2
4405.94, 1016.76, 95.55 Radius 4
North 1
4413.37, 813.86 91.57 Radius 5
North 2
4404.45, 802.42, 89.99 Radius 5
If you do change to add blackspots (which seems like perhaps a nice solution since it got stuck on them again while trying to get to a mob, although got itself unstuck) then you'll probably also want to enable ignoreblackspots on the following as the barrels are very close to the fortifications
Questing in Kun Lai Summit. Level 89. Horde.
Bot been running really smooth pretty much AFK since my last post, which is the majority of Kun Lai, so kudos to the team!
I've hit an issue where it's got stuck. My last three characters through here have got stuck in exactly the same spot, and the unstuck routine wasn't running at all.
Specifically we're in Zouchin Village, coming up the northern path to the village, and getting stuck on the woodern fortifications.
Now I know normally these issues should go to the Navigational thread, but please hear me out and don't hit me with the "not-a-profile-issue" stick!

There's a couple of reasons I'm raising it here, rather than the Nav thread:
- When it gets stuck, the profile is using the CustomBehavior "NoCombatMoveTo", which at present seems to have no unstuck logic and seemingly quite happily faceplants a wall or obstacle endlessly. To me this is something that should be sorted ASAP.
- The area is heavily phased and the obstacle it gets stuck on only exists while in certain points of the quest chain; I know historically such things have been difficult to mesh (please correct me if things have changed recently).
- Since we're coming via a set path, from a specific quest down the hill, I think this is quite easy to solve in the quest profile itself, and so can be sorted relatively quickly.
So, looking at the current profile. Line 2389 onwards:
Code:
<If Condition="((!HasQuest(31011)) && (!IsQuestCompleted(31011)))" >
<PickUp QuestName="Enemies At Our Door" QuestId="31011" GiverName="Lorewalker Cho" GiverId="61371" X="4406.11" Y="939.1094" Z="116.0033" />
<CustomBehavior File="WaitTimer" WaitTime="2000" GoalText="Waiting for scene {TimeRemaining}" />
<CustomBehavior File="Misc\RunLua" Lua="StopCinematic()" WaitTime="1000" />
<RunTo X="4413.25" Y="807.2814" Z="87.98991" />
</If>
<If Condition="((HasQuest(31011)) && (!IsQuestCompleted(31011)))" >
<CustomBehavior File="UserSettings" PullDistance="1" />
<!--<RunTo X="4382.372" Y="1011.066" Z="98.62169" />-->
<While Condition="((HasQuest(31011)) && (!IsObjectiveComplete(2, 31011)))"> <!-- Roll barrels into 5 Behemoths -->
<CustomBehavior File="NoCombatMoveTo" X="4382.372" Y="1011.066" Z="98.62169" />
<CustomBehavior File="InteractWith" QuestId="31011" MobId="62591" CollectionDistance="10" WaitTime="500" X="4401.267" Y="1010.197" Z="96.01667" />
</While>
Now, that first RunTo (4413,807,87) take it to standing just next to the obstacle. The following NoCombatMoveTo takes it on a path right through the wooden fortification, which seemingly isn't meshed.
I would propose another intermediate step, with NoCombatMoveTo going to 4403.85, 812.43, 91.51, which would move it just past the fortification.
So, change as follows:
Code:
<If Condition="((!HasQuest(31011)) && (!IsQuestCompleted(31011)))" >
<PickUp QuestName="Enemies At Our Door" QuestId="31011" GiverName="Lorewalker Cho" GiverId="61371" X="4406.11" Y="939.1094" Z="116.0033" />
<CustomBehavior File="WaitTimer" WaitTime="2000" GoalText="Waiting for scene {TimeRemaining}" />
<CustomBehavior File="Misc\RunLua" Lua="StopCinematic()" WaitTime="1000" />
<RunTo X="4413.25" Y="807.2814" Z="87.98991" />
</If>
<CustomBehavior QuestId="31011" File="NoCombatMoveTo" X="4403.85" Y="812.43" Z="91.51" /> <!-- Added to avoid getting stuck on wooden fortification -->
<If Condition="((HasQuest(31011)) && (!IsQuestCompleted(31011)))" >
<CustomBehavior File="UserSettings" PullDistance="1" />
<!--<RunTo X="4382.372" Y="1011.066" Z="98.62169" />-->
<While Condition="((HasQuest(31011)) && (!IsObjectiveComplete(2, 31011)))"> <!-- Roll barrels into 5 Behemoths -->
<CustomBehavior File="NoCombatMoveTo" X="4382.372" Y="1011.066" Z="98.62169" />
<CustomBehavior File="InteractWith" QuestId="31011" MobId="62591" CollectionDistance="10" WaitTime="500" X="4401.267" Y="1010.197" Z="96.01667" />
</While>
I considered putting inside the "If" block of the previous quest, but figured that if the user stopped and started after completing the previous quest, it's probably best to run it anyway and get to a "safe" spot.
Let me know your thoughts...
Edit: Tested and working
Edit2: As an afterthought - would small blackspots work for these unmeshed obstacles?
If blackspots would work then here they are:
East 1
4407.13, 1004.90, 95.19 Radius 4
East 2
4405.94, 1016.76, 95.55 Radius 4
North 1
4413.37, 813.86 91.57 Radius 5
North 2
4404.45, 802.42, 89.99 Radius 5
If you do change to add blackspots (which seems like perhaps a nice solution since it got stuck on them again while trying to get to a mob, although got itself unstuck) then you'll probably also want to enable ignoreblackspots on the following as the barrels are very close to the fortifications
Code:
<CustomBehavior File="InteractWith" QuestId="31011" MobId="62591" CollectionDistance="10" WaitTime="500" X="4401.267" Y="1010.197" Z="96.01667" />