Pathfinding Events Change

About the 6th of September Maestro Linden updated the Pathfinding Events. See the Wiki page: Event path_update. I hadn’t looked at the page for some time. So, I had not noticed until now.

Events are triggers for scripts. They are sort of thing that says: this just happened. You then have a chance to have the script do something in response. The Pathfinding events now include these things:

  1. PU_SLOWDOWN_DISTANCE_REACHED
  2. PU_GOAL_REACHED
  3. PU_FAILURE_INVALID_START
  4. PU_FAILURE_INVALID_GOAL
  5. PU_FAILURE_UNREACHABLE
  6. PU_FAILURE_TARGET_GONE
  7. PU_FAILURE_NO_VALID_DESTINATION
  8. PU_EVADE_HIDDEN
  9. PU_EVADE_SPOTTED
  10. PU_FAILURE_NO_NAVMESH
  11. PU_FAILURE_DYNAMIC_PATHFINDING_DISABLED
  12. PU_FAILURE_PARCEL_UNREACHABLE
  13. PU_FAILURE_OTHER

The green items are new.

Being able to detect when a region has disabled Pathfinding allows the scripter to move the character out of the area and restart it. That will stop PF Characters from piling up at the borders of disabled regions.

When I looked at the page the links from these items had not been added yet. So, we don’t have detailed information on each event. For instance at what distance does PU_SLOWDOWN_DISTANCE_REACHED trigger? Can one set the distance?

Eventually the pages will get written and appear. Until then we’ll just have to go with the short descriptions provided on the path_update page.

 

2 thoughts on “Pathfinding Events Change

  1. I think that PU_SLOWDOWN_DISTANCE_REACHED only triggers when WANDER_PAUSE_AT_WAYPOINTS is set as an option in llWanderWithin or llPatrolPoints . I can’t see anything in the the specs for those functions to control when exactly it fires.

    • Several points are rather fuzzy… I add to the wiki when I am sure I have something figured out.

Leave a Reply

Your email address will not be published.