Fly to hotspots in grind profiles?

[r00t]

The latest version of HB broke my (admittedly) hackish way of forcing the bot to fly to hotspots while grinding volatiles. Is there now a way to have HB fly to hotspots in a normal grind profile?

I can no longer grind my volatiles with a flying mount which really sucks and makes the bot stick out like a sore thumb.

 

[chinajade]

The latest version of HB broke my (admittedly) hackish way of forcing the bot to fly to hotspots while grinding volatiles. Is there now a way to have HB fly to hotspots in a normal grind profile?

I'm curious as to you previously solved this problem.

As we all know, Honorbuddy does not have native built-in flying facilities. The only work-arounds to this, that I know are:

1) Use the LetMeFly plugin (and the LetMeFly Helper plugin is a wonderful adjunct for it),

2) Convert a 'Grinding' profile, and to a "Questing" profile that uses <SetGrindAreas>.
You would then break the grind areas up into smaller pieces and use the <FlyTo> behavior to navigate among them.​

I know this isn't what you want to hear. It would be really nice to have built-in flying for those repair, vendor, and mailbox runs also, but alas I've resigned myself that built-in flying will never happen.


cheers,
chinajade

 

[r00t]

I'm curious as to you previously solved this problem.

As we all know, Honorbuddy does not have native built-in flying facilities. The only work-arounds to this, that I know are:

1) Use the LetMeFly plugin (and the LetMeFly Helper plugin is a wonderful adjunct for it),

2) Convert a 'Grinding' profile, and to a "Questing" profile that uses <SetGrindAreas>.
You would then break the grind areas up into smaller pieces and use the <FlyTo> behavior to navigate among them.​

I know this isn't what you want to hear. It would be really nice to have built-in flying for those repair, vendor, and mailbox runs also, but alas I've resigned myself that built-in flying will never happen.


cheers,
chinajade

I'll have to give your second method a try...I was using a really dirty method of having a questing profile with the following:

<QuestOrder>
<While Condition="HasQuest(25020)">
<CustomBehavior File="ForcedMount" QuestId="10238" MountType="Flying" />
<CustomBehavior File="SetPullDistance" Distance="1" />
<CustomBehavior File="FlyTo" X="-9797.234" Y="155.2109" Z="85.75282" />
<CustomBehavior File="SetPullDistance" Distance="40" />
<!-- Next HotSpot -->
<CustomBehavior File="ForcedMount" QuestId="10238" MountType="Flying" />
<CustomBehavior File="SetPullDistance" Distance="1" />
<CustomBehavior File="FlyTo" X="-9874.772" Y="150.3141" Z="68.99361" />
<CustomBehavior File="SetPullDistance" Distance="40" />
<!-- Next HotSpot -->
and so on and so forth...

The quest you have doesn't matter so long as you still have that quest when u start the profile. The thing that HB broke in the latest release was the SetPullDistance. In my grind profile, once you flew to a spot that was in range of a Scion of Al'akir (in this example), SetPullDistance would force you to dismount and kill the mob. Rinse and repeat. Yea, the order of hotspots is the same every time around, but pretty much everyone else looks the same while they are farming there so you blend in. People don't think to report bots that are flying to mobs and killing them, because that's what everyone else is doing.

LetMeFly is a nice idea, but unfortunately it still looks like a bot. This is especially apparent when you have to hit multiple waypoints while moving to a hotspot. The mount will dive bomb into the ground and jump up and dive bomb again. Really bad when you are going around corners.


Question for you: In your example with <SetGrindArea>, what would your <GrindTo> condition be so that you could break out of the grind area and move to the next one?

 

[chinajade]

I'll have to give your second method a try...I was using a really dirty method of having a questing profile with the following:

I like your approach!

There have been some behavior changes that will help you out with it...

• FlyTo
  With the latest FlyTo, you should no longer require calls to the PullDistance behavior. FlyTo now automatically set PullDistance to 1 (internally) while the behavior is in progress. FlyTo now also turns off all harvests and other such things such that there are no distractions during movement. The original PullDistance and harvest settings are restored when the behavior is done, or the bot is stopped.
  
  
• ForcedMount
  No longer requires the QuestId
  
  
• ForcedDismount
  Now exists thanks to Bobby53. Its smart enough to descend before dismount, so you don't have to get FlyTo's Z coordinate exactly right.

And you missed the trick of Condition="true" to put things in an endless loop. E.g., you don't need a HasQuest() in the While Condition.

So, using your technique, and the new behaviors, your profile reduces to the following...

<QuestOrder>
    <While Condition="true">
        <CustomBehavior File="ForcedMount" MountType="Flying" />
        <CustomBehavior File="FlyTo" X="-9797.234" Y="155.2109" Z="85.75282" />
        <CustomBehavior File="ForcedDismount" />
    
        <!-- Next HotSpot -->
        <CustomBehavior File="ForcedMount" MountType="Flying" />
        <CustomBehavior File="FlyTo" X="-9874.772" Y="150.3141" Z="68.99361" />
        <CustomBehavior File="ForcedDismount" />
    
        <!-- ... -->
    </While>
</QuestOrder>

Very clever indeed! Thanks for sharing.

LetMeFly is a nice idea, but unfortunately it still looks like a bot. This is especially apparent when you have to hit multiple waypoints while moving to a hotspot. The mount will dive bomb into the ground and jump up and dive bomb again. Really bad when you are going around corners

That is precisely the problem solved by the LetMeFly Helper adjunct plugin. It'd be nice if both were rolled into one. If you haven't tried the Helper, grab it, and give LetMeFly a second look. You may be pleased unless there is some awkward terrain in the area.

In your example with <SetGrindArea>, what would your <GrindTo> condition be so that you could break out of the grind area and move to the next one?

It would be a bit clunky (and this is untested, but _should_ work)...

<QuestOrder>
    <SetGrindArea>
        <!-- ...whatever... -->
        <Hotspot X="-9797.234" Y="155.2109" Z="85.75282" />
        <Hotspot X="-9874.772" Y="150.3141" Z="68.99361" /> <!-- last hotspot in this area -->
    </SetGrindArea>

    <!-- Grind until we are within 3 yards of our last hotspot -->
    <GrindTo Condition="Me.Location.Distance(new WoWPoint(-9874.772, 150.3141, 68.99361)) &lt; 3.0" />
</QuestOrder>

Either way, you're still screwed with vendor/repair runs unless you figure out a way to do them pro-actively.

cheers,
chinajade

 

[r00t]

Thanks for all the great info. Hopefully I can be back to farming volatiles tonight!

As for repair/vendor, you could probably do them with an If condition where you could check your durability or bag space if you can make a call like that in a profile. Could check every couple of grind areas.

 

[soussi]

I grind while flying in some cases, what u i do:
- Start the grinding profile as GB2
- use the builtinplugin in rarekiller to attack the given ID of the mob.

I hope someone could make a seperate plugin to be able to input more IDs and even faction IDs if possible.
The rarelkiller plugin works like a charm and aslo has a blacklist mob feature. Downside is it only reads one ID.

Just tought to bring it up as it may help some peeps