Maybe Better Solution of "Unsticking"

[j19861986]

I have thought about unsticking bot
If it can't unstick 2 times, bot tries to get in one step back (example to waypoint 15) and lua code using

Code: Select all

__WPL:setWaypointIndex( __WPL:getNearestWaypoint(player.X, player.Z, player.Y ) );

and try to get the nearest waypoint from current position (in x,y,z position)... If it doesn't work then it tries to get backwards one more step again (this time waypoint 14) and tries

Code: Select all

__WPL:setWaypointIndex( __WPL:getNearestWaypoint(player.X, player.Z, player.Y ) );

to get nearest waypoint from current position (x,y,z position)... if it doesn't help it will go back to waypoint 13 and try

Code: Select all

__WPL:setWaypointIndex( __WPL:getNearestWaypoint(player.X, player.Z, player.Y ) );

then maybe it can go back to current track again...
Or maybe you have a better idea to unstick bot
give examples, cause I am tired getting logged out while running instances (looting, and selling)

[j19861986]

And maybe come forward couple of times and using

Code: Select all

__WPL:setWaypointIndex( __WPL:getNearestWaypoint(player.X, player.Z, player.Y ) );

example: go forward one step at a time and using the lua code after going back wasn't a solution...

[lisa]

I actually put in some code for people to be able to customise what happens when the bot sticks. You could test out your theories and see how they do just be adding in some user functions.

Code: Select all

unStick3()
unStick6()
unStick9()

If you have any of these functions it will do your code instead of the default at that number of unsticks.

[Auto Pilot]

About the cause of stucks. For me most of them were caused by some kind of lag : bots walks too far after waypoint, tries to correct position but has already fallen somewhere and can't do anything without some help. What I've learned from it :
- Mounts (especially a 70% one) are really bad when there might be any kind of lag/slowdown/...
- Not sure if normal runbuffs (title & house pots) speed up the char enough to be responsible for those distance breaks too
- Make waypoints as far as possible from those "danger zones" helps to give the bot some margin before it gets stuck
- If stuck problems always happen in the same place then loading a specific waypoint file to unstuck is a good idea (so the bot always uses an unstuck path and can't even try to run back again to the "on top of the cliff"/... waypoint)

And nice addition Lisa, this will help a bit more with stuck issues