What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Help with a quest

blacklisted

New Member
Joined
Jan 15, 2010
Messages
224
Reaction score
1
I'm making a quest profile and I have ran into a problem with is quest.
Flamebreaker - Quest - World of Warcraft


The toon will run to the NPC and attack it instead of using the Flameseer's staff on it.
any ideas where the code is wrong.
I have the following code within the quest order tags
HTML:
<UseItem ItemId="53107" QuestId="25323" TargetId="38896" TargetType="Npc"  X="5239.005" Y="-2848.203" Z="1544.786" />
<UseItem ItemId="53107" QuestId="25323" TargetId="38896" TargetType="Npc"  X="5277.059" Y="-2833.028" Z="1526.515" />
<UseItem ItemId="53107" QuestId="25323" TargetId="38896" TargetType="Npc"  X="5243.947" Y="-2792.81" Z="1531.611" />
<UseItem ItemId="53107" QuestId="25323" TargetId="38896" TargetType="Npc"  X="5378.166" Y="-2966.753" Z="1548.387" />
<UseItem ItemId="53107" QuestId="25323" TargetId="38896" TargetType="Npc"  X="5349.064" Y="-3000.562" Z="1550.952" />

And below is what I have as an override,
HTML:
<Quest Id="25323" Name="Flamebreaker">
    <Objective Type="KillMob" MobId="40065" KillCount="30">
      <Hotspots>
        <Hotspot X="5239.005" Y="-2848.203" Z="1544.786" />
        <Hotspot X="5277.059" Y="-2833.028" Z="1526.515" />
        <Hotspot X="5243.947" Y="-2792.81" Z="1531.611" />
        <Hotspot X="5378.166" Y="-2966.753" Z="1548.387" />
        <Hotspot X="5349.064" Y="-3000.562" Z="1550.952" />
       </Hotspots>
    </Objective>
  </Quest>
 
I'm not sure what the proper Profile "pattern" is for these types of quests. You might try commenting out the override, and altering your quest order to:

Code:
 &lt;QuestOrder&gt;
     &lt;Pickup... &gt;
      &lt;UseItem ItemId="53107" QuestId="25323" TargetId="38896" TargetType="Npc"  X="5239.005" Y="-2848.203" Z="1544.786" /&gt;
      &lt;Objective  QuestId="25323" Type="KillMob" MobId="40065" KillCount="1"&gt;

      &lt;!-- Repeat... --&gt;
      &lt;UseItem ItemId="53107" QuestId="25323" TargetId="38896" TargetType="Npc"  X="5239.005" Y="-2848.203" Z="1544.786" /&gt;
      &lt;Objective  QuestId="25323" Type="KillMob" MobId="40065" KillCount="2"&gt;

      &lt;!-- Repeat these lines 27 more times... --&gt;
      &lt;UseItem ItemId="53107" QuestId="25323" TargetId="38896" TargetType="Npc"  X="5239.005" Y="-2848.203" Z="1544.786" /&gt;
      &lt;Objective  QuestId="25323" Type="KillMob" MobId="40065" KillCount="3"&gt;

     &lt;TurnIn... &gt;

 &lt;/QuestOrder&gt;

Note that we bump the "KillCount" each time the Objective line is repeated (until we get to 30).

The fundamental problem is we don't want to kill the mobs in the quest override, we want to &lt;UseItem&gt; on them, then kill the mobs that are the result of that action. But the override is our only vehicle for locating the mobs for using the item.

Even if this suggestion works, there are a number of downsides:
  • There are probably several little mobs that spawn out of the larger one when you use the item--maybe 1 or maybe 5. But we can't depend on more than 1, so we'll be using the item a lot more than necessary.
  • To my understanding, the 'targeted' version of &lt;UseItem&gt; requires the specification of X-Y-Z coordinates at this time. If there is no mob at the specified X-Y-Z coordinates, I've no idea what Honorbuddy will do. Standaround? Move to next objective? Something else?


We probably need to create a pattern catalog for quest types. This would be one fine example. But to be honest, I'm not sure how to do it cleanly at the moment.

If you can't get it to work, please submit a Bugtracker report so that we can get some proper machinery for doing these kinds of quests.

cheers,
CJ
 
Thanks for the help ill give it a go tomorrow, Thanks for the help.
 
Hi I gave it a bash and it still would'nt use the quest item but just engage in combat.
I did notice tho that id the NPC wasn't at the location HB would move onto the next hotspot.

I will submit a bug report.
 
Back
Top