Problem with QuestOrder

panYama · Jan 21, 2011

I'm building up my Profile for wintersaber trainers again and tried to update it.

but apparently HB hates doing the overrides for me at all.

HTML:

   <Objective Type="CollectItem" ItemId="12622" CollectCount="5">
    <CollectFrom>
     <Mob Name="Shardtooth Bear" Id="7444"/>
    </CollectFrom>
    <Hotspots>
     <Hotspot X="7650.95" Y="-4252.917" Z="661.5635" />
     <Hotspot X="7614.726" Y="-4292.393" Z="640.1373" />
     <Hotspot X="7566.894" Y="-4370.571" Z="614.1542" />
     <Hotspot X="7555.589" Y="-4489.822" Z="605.6418" />
     <Hotspot X="7499.796" Y="-4533.177" Z="606.113" />
     <Hotspot X="7522.363" Y="-4596.941" Z="628.525" />
    </Hotspots>
   </Objective>

As you can see it should kill some NPC for item Shardtooth meat x 5 is received.
Problem tough, it will walk pas those mobs not attacking them or anything.

Then when they do get aggro the NPC does appear on the targetlist and gets killed.
So it seems like hb is ignoring the mobs on the targetlist, where it in previous versions didn't so how come my targets defined by this override don't show up on the targetlist?

Things i've tried:
- delete meshes
- Change CollectItem to KillMob
- Swapping tags around
- looking into old profile pasted those coords in and id's
- added removed a bunch of stuff

all of these failed to work.
How can this problem be solve in a normal fashion, if any of you has a proper awnser to that I'd be more then thankfull as I've just wasted 2 hours on that.

ps. that code is a small part of the override.

chinajade · Jan 21, 2011

I know you know to check things like 'pull distance', and kill between hotspots and all. So, I'll go out on a limb with 100% conjecture...

It may be that the initialization of 'current grind area' has been altered somewhere in the chain of Honorbuddy releases. At the very beginning of your profile, set up a <SetGrindArea> (that will never be used). But, be sure the TargetMin/TargetMaxLevels, Factions, and MaxDistance are set up. If this solves the problem, then we know its an HB bug with bad initialization for profiles that don't establish a 'current grind area' somewhere along the way.

Just a completely wild guess.

cheers,
chinajade

panYama · Jan 21, 2011

ill try thanks for the suggestion you will hear from me within an hour to see if it works.

regards,
panYama

Nuok · Jan 21, 2011

Just use the new grind until isquestcomplete() its much more versatile than the overrides are.

There should be an example on the wiki

<GrindTo Condition="IsQuestComplete()">

Make sure you set up the grind area first ofc

panYama · Jan 21, 2011

Nuok said:
Just use the new grind until isquestcomplete() its much more versatile than the overrides are.

There should be an example on the wiki

<GrindTo Condition="IsQuestComplete()">

Make sure you set up the grind area first ofc

its a quest so not sure if the grind area will work since you dont put it in questoverride. so and maybe can you link the wiki?

Nuok · Jan 21, 2011

panyama said:
its a quest so not sure if the grind area will work since you dont put it in questoverride. so and maybe can you link the wiki?

All it will do is grind until the quest is complete; you can set the condition to anything you like. Its almost like telling it too kill these mobs until the quest is finshed. This would replace your objective for the quest.

http://www.thebuddyforum.com/mediawiki/index.php?title=Honorbuddy_Profile_Tag:_GrindTo

panYama · Jan 21, 2011

got the wiki link for me?

chinajade · Jan 21, 2011

panYama said:
can you link the wiki?

The page has been updated to reflect the new Conditional= attribute:

[wiki]Honorbuddy Profile Tag: GrindTo[/wiki]

cheers,
chinajade

panYama · Jan 21, 2011

thanks appriciate it.

regards,
panYama

panYama · Jan 21, 2011

chinajade said:
I know you know to check things like 'pull distance', and kill between hotspots and all. So, I'll go out on a limb with 100% conjecture...

It may be that the initialization of 'current grind area' has been altered somewhere in the chain of Honorbuddy releases. At the very beginning of your profile, set up a <SetGrindArea> (that will never be used). But, be sure the TargetMin/TargetMaxLevels, Factions, and MaxDistance are set up. If this solves the problem, then we know its an HB bug with bad initialization for profiles that don't establish a 'current grind area' somewhere along the way.

Just a completely wild guess.

cheers,
chinajade

Where exactly in the quest order should I place this? because i've tried setting it up and it kept grinding those mobs but it didn't work.

panYama · Jan 24, 2011

anyone to help now?

killakaz · Jan 24, 2011

panyama said:
Where exactly in the quest order should I place this? because i've tried setting it up and it kept grinding those mobs but it didn't work.

For a quest order it would be as follows

PHP:

  <SetGrindArea>
      <GrindArea>
        <Factions>22 19 189</Factions>
        <TargetMinLevel>14</TargetMinLevel>
        <TargetMaxLevel>18</TargetMaxLevel>
        <Hotspots>
          <Hotspot X="-9708.577" Y="-2297.818" Z="65.19514" />
          <Hotspot X="-9707.625" Y="-2137.688" Z="60.02473" />
          <Hotspot X="-9805.584" Y="-2163.874" Z="62.03535" />
          <Hotspot X="-9728.514" Y="-2203.698" Z="58.96577" />
          <Hotspot X="-9701.276" Y="-2279.798" Z="60.84199" />
          <Hotspot X="-9599.462" Y="-2235.299" Z="88.99763" />
          <Hotspot X="-9529.56" Y="-2231.735" Z="82.83737" />
          <Hotspot X="-9469.197" Y="-2319.276" Z="68.60277" />
          <Hotspot X="-9503.464" Y="-2386.341" Z="58.5433" />
          <Hotspot X="-9531.088" Y="-2368.263" Z="73.97243" />
          <Hotspot X="-9546.84" Y="-2284.777" Z="75.31286" />
          <Hotspot X="-9618.018" Y="-2314.959" Z="72.03002" />
          <Hotspot X="-9735.854" Y="-2277.737" Z="63.13863" />
        </Hotspots>
      </GrindArea>
    </SetGrindArea>
    <Grindto Level="18"/>

panYama · Jan 24, 2011

killakaz said:
For a quest order it would be as follows

PHP:

<SetGrindArea> <GrindArea> <Factions>22 19 189</Factions> <TargetMinLevel>14</TargetMinLevel> <TargetMaxLevel>18</TargetMaxLevel> <Hotspots> <Hotspot X="-9708.577" Y="-2297.818" Z="65.19514" /> <Hotspot X="-9707.625" Y="-2137.688" Z="60.02473" /> <Hotspot X="-9805.584" Y="-2163.874" Z="62.03535" /> <Hotspot X="-9728.514" Y="-2203.698" Z="58.96577" /> <Hotspot X="-9701.276" Y="-2279.798" Z="60.84199" /> <Hotspot X="-9599.462" Y="-2235.299" Z="88.99763" /> <Hotspot X="-9529.56" Y="-2231.735" Z="82.83737" /> <Hotspot X="-9469.197" Y="-2319.276" Z="68.60277" /> <Hotspot X="-9503.464" Y="-2386.341" Z="58.5433" /> <Hotspot X="-9531.088" Y="-2368.263" Z="73.97243" /> <Hotspot X="-9546.84" Y="-2284.777" Z="75.31286" /> <Hotspot X="-9618.018" Y="-2314.959" Z="72.03002" /> <Hotspot X="-9735.854" Y="-2277.737" Z="63.13863" /> </Hotspots> </GrindArea> </SetGrindArea> <Grindto Level="18"/>

<setgrindarea><grindarea><hotspots><hotspot x="-9708.577" y="-2297.818" z="65.19514"><hotspot x="-9707.625" y="-2137.688" z="60.02473"><hotspot x="-9805.584" y="-2163.874" z="62.03535"><hotspot x="-9728.514" y="-2203.698" z="58.96577"><hotspot x="-9701.276" y="-2279.798" z="60.84199"><hotspot x="-9599.462" y="-2235.299" z="88.99763"><hotspot x="-9529.56" y="-2231.735" z="82.83737"><hotspot x="-9469.197" y="-2319.276" z="68.60277"><hotspot x="-9503.464" y="-2386.341" z="58.5433"><hotspot x="-9531.088" y="-2368.263" z="73.97243"><grindto level="18"></grindto></hotspot></hotspot></hotspot></hotspot></hotspot></hotspot></hotspot></hotspot></hotspot></hotspot></hotspots></grindarea></setgrindarea>

my thought *Yawn*.... I know this but since the whole normal order is bugged I have to override it with that but when I do so it doesn't care about the GrindTo tag... so it keeps farming 1 mob over and over..

killakaz · Jan 24, 2011

well currently in latest version of HB collectitem tag is not working properly that may be your issue
it works in previous version.
i also have quests that won't collect things cause of this yet if you run it with previous version it runs fine

Kickazz006 · Jan 24, 2011

what about:

PHP:

<If Condition="(HasQuest())" > or maybe this: <If Condition="(IsQuestCompleted())">
    <objective />
     <ElseIf>
              setga / ga / factions / hotspots ////
     </ElseIf>
</If>

or something like that?

I'm trying something like this, but it's not working correctly (ignore the runmacro, i haven't updated this for newest HB as it's nav is buggy) and I don't know how to say "if the quest is not completed" as !IsQuestCompleted() the bot just ignores

PHP:

			<If Condition="((HasItem(36940)) &amp;&amp; (!HasQuest(12105)) &amp;&amp; (!IsQuestCompleted(12105)))" >
				<CustomBehavior File="RunMacro" Macro="/use Mikhail's Journal" NumOfTimes="1" WaitTime="1000" />
				<CustomBehavior File="RunMacro" Macro="/script AcceptQuest()" NumOfTimes="1" WaitTime="1000" />
			<ElseIf Condition="((!HasItem(36940)) &amp;&amp; (!HasQuest(12105)) &amp;&amp; (!IsQuestCompleted(12105)))">
				<SetGrindArea>
					<GrindArea>
						<Factions>16</Factions> <!-- [Silverbrook Hunter] -->
						<Hotspots>
					                 <!-- deleted -->
						</Hotspots>
					</GrindArea>
				</SetGrindArea>
			</ElseIf>
			</If>

panYama · Jan 25, 2011

sorry but I don't get the code kickazz and so basically CollectItem is broken?

Kickazz006 · Jan 25, 2011

panyama said:
sorry but I don't get the code kickazz and so basically CollectItem is broken?

For your particular quest, I don't know... but I think it's wanting to think that it has to collect from something else instead of the bears and chimera

PHP:

 <If Condition="((HasQuest(#)) && (IsQuestCompleted(#)))" >
                <Objective />
                <Objective />

            <ElseIf Condition="((HasQuest(#)) && (!IsQuestCompleted(#)))">
                <SetGrindArea>
                    <GrindArea>
                        <Factions></Factions> <!-- [Bears, Chimera] -->
                        <Hotspots>
                               <Hotspot X Y Z />
                               <Hotspot X Y Z />
                               <Hotspot X Y Z />
                        </Hotspots>
                    </GrindArea>
                </SetGrindArea>
            </ElseIf>

</If>

I dunno, i've been playing with this and it's been a bugger =(

panYama · Jan 25, 2011

Kickazz006 said:
For your particular quest, I don't know... but I think it's wanting to think that it has to collect from something else instead of the bears and chimera

PHP:

<If Condition="((HasQuest(#)) && (IsQuestCompleted(#)))" > <Objective /> <Objective /> <ElseIf Condition="((HasQuest(#)) && (!IsQuestCompleted(#)))"> <SetGrindArea> <GrindArea> <Factions></Factions>  <Hotspots> <Hotspot X Y Z /> <Hotspot X Y Z /> <Hotspot X Y Z /> </Hotspots> </GrindArea> </SetGrindArea> </ElseIf> </If>

I dunno, i've been playing with this and it's been a bugger =(

it that working that u have right there? or not tested yet?

also I do like a work around but it's a pain that the core feature doesnt work and so i have to work around it each time it wants to do the quest which makes the profile longer and longer.

Kickazz006 · Jan 25, 2011

panyama said:
it that working that u have right there? or not tested yet?

also I do like a work around but it's a pain that the core feature doesnt work and so i have to work around it each time it wants to do the quest which makes the profile longer and longer.

It's just an example, I haven't gotten the time to test it out. I've been trying to get northrend QO up and running (at least 40-60 quests per zone) before i do "fancy" stuff

ie: my borean has ~100 quests completed (i think 95 were by bot)

my grizzly hills has ~45 or 50 (at least 40 by bot)

and the reason I have a few quests not done by bot is that I did them but the bot would work properly (stuff like findend/startpoly problems) or it wouldn't run somewhere properly.

panYama · Jan 25, 2011

nice, well ill have a look a bit later on.
where do I place that tough?

within or out the quest order and if so after the pickup or before?

Problem with QuestOrder

Community Developer

Community Developer

Community Developer

Community Developer

Community Developer

Community Developer

Community Developer

Community Developer

Community Developer

Community Developer

Community Developer

Community Developer

Community Developer

Community Developer

Well-Known Member

Community Developer

Well-Known Member

Community Developer

Well-Known Member

Community Developer