Profile doesnt continue after zoning

[jagarock]

Im making a profile, but having trouble continuing the script after it zones out of a dungeon.

The dungeon exit is the typical big blue shit.
And ive set it up like this to run into it:

<RunTo X="-726.3634" Y="2.68129" Z="-248.05" />

And the bot runs there, and gets zoned out, all is fine.

But when its zoned out of the dungeon, it still tries to reach the same destination. It doesnt continue on to the next step, so it fails and stops.

How do people do this? There should be a <Try> , or even a "If RunTo fails after 5 seconds, continue to next step instead of exiting".

 

[Tony]

http://www.thebuddyforum.com/honorb...-how-attach-your-hb-db-log-file-pictures.html

 

[jagarock]

solved this by stopping right before the gate and running a /cast Teleporter Beast macro since im running a druid.

 

[jagarock]

actually, that didnt work. its not possible to use a spell to exit a dungeon.

so i need to use the functions.

i attached the log here : View attachment 3996 2014-05-09 08.56.txt

as you can clearly see, from the log, it still tries to move to the set destination (the exit point of the dungeon from line 1769), even after it has zoned out into azeroth.

how can this be avoided?

1769 : [07:05:54.037 D] Goal: Moving to <-727.1, -0.01, -248.04>
## This is the exitpoint of the dungeon, and now it zones out.
1772 : [07:05:56.511 D] Changed map(s) to Azeroth
## Now we're out, and it still tries to reach this destination. fml.
1843 : [07:06:00.950 D] Could not generate path from {-12412.5, 232.731, 0.9266032} to {-727.1, -0.01, -248.04} (time used: 0 milliseconds) @ FindEndPoly

 

[chinajade]

Hi, Jagarock,

Give a look at the GoThruPortal quest behavior. It was designed to go through these types of portals.

The other type of portals—the ones you have to click on—are addressed with the InteractWith quest behavior.

cheers,
chinajade

 

[EchoTiger]

Traditionally we'd use a CTM to navigate in/out of an instance.
The reason CTM is used instead of RunTo is because not every instance portal has collision on the ground behind it, which can cause navigation errors.

To obtain the CTM coordinate, we would walk through the instance, then as the game is loading generate the coordinate.
That way we have solid coordinate that wont cause hiccups.

If you generate a coordinate too far into the instance, then the bot will never reach the coordinate before the game starts loading.
Which this is most-likely what's happening to your profile.
Since the coordinate is never 'reached' the bot continues to navigate to it after the loading sequence.

After the bot CTMs into the portal, we would use a WaitTimer to pause the bots actions.
That way the game client has time to load before any further execution of the profile is rendered.
If the WaitTimer is not added, then the bot will try to navigate to the next coordinate while the client is loading.
Which this of course causes further errors.

However, like I said this is more of a traditional method.
If I were you, I would use GoThruPortal as Chinajade suggested. :3