chinajade
Community Developer
- Joined
- Jul 20, 2010
- Messages
- 17,540
Profile: [Fly][H - Quest] LK 68-80 [Kick]
Quest: The Runic Prophecies - Quest - World of Warcraft
Description: Better landing Point Handling. Otherwise it sometime Stucks.
Profile: [Fly][A - Quest] LK 68-80 [Kick]
Quest: The Runic Prophecies - Quest - World of Warcraft
Descirption: Remove Quest Override + Changed InteractWith to Objective Type="UseObject"
Hi, MaxMuster,
We went with a slightly different stop-start friendly change that looks like this:
<While Condition="HasQuest(12058) && !IsQuestCompleted(12058)">
<CustomBehavior File="InteractWith" QuestId="12058" QuestObjectiveIndex="3"
</While>MobId="188289" CollectionDistance="10"
X="4952.656" Y="-4705.741" Z="219.8488" />
<CustomBehavior File="InteractWith" QuestId="12058" QuestObjectiveIndex="1"X="4952.656" Y="-4705.741" Z="219.8488" />
MobId="188264" CollectionDistance="10"
X="5007.675" Y="-4734.232" Z="219.4391" />
<CustomBehavior File="InteractWith" QuestId="12058" QuestObjectiveIndex="2"X="5007.675" Y="-4734.232" Z="219.4391" />
MobId="188288" CollectionDistance="10"
X="5006.924" Y="-4790.667" Z="219.4593" />
<CustomBehavior File="WaitTimer" QuestId="12058" WaitTime="10000"X="5006.924" Y="-4790.667" Z="219.4593" />
GoalText="Waiting for quest to complete {TimeRemaining}" />
We did this such that the Alliance-side and Horde-side quest would have the same (simplified, but stop-start friendly) profile code. If you feel that this was the wrong approach, please let us know.
The changes are folded into v3046.
cheers,
chinajade
[size=-2]Ref: [post=1371408]MaxMuster's Horde problem report w/recommended repair[/post][/size]
[size=-2]Ref: [post=1371413]MaxMuster's Alliance problem report w/recommended repair[/post][/size]