nav
ARES System Manual: nav Application
The following additional commands require that the region have an ANav Server:
The navigation system allows the unit to automatically move to a target place or object. This is accomplished mainly by walking using a mixture of direct movement and SL pathfinding, although the tp/warp/jump command will teleport the unit directly.
Importantly,
To navigate to a named destination, the region must have a navigation server that provides a list of named destinations and their coordinates. This is intended for roleplay.
In Companion, the module
Settings
The
Note: Most values from the settings database are not automatically applied after modification. Affected programs must be restarted (e.g. with
nav follow [<key>]
: follow the specified key, or, if none specified, follow the invoking avatar
nav stop
: terminate navigation or following
nav bookmark <name> remove|here|<slurl>
: manages a TP bookmark
nav add <name> here|<slurl>
: synonym for nav bookmark
nav remove <name>
: synonym for nav bookmark <name> remove
nav tp|warp|jump <name>|<slurl>|me
: teleports the unit to a bookmark, SLURL, or the user
The following additional commands require that the region have an ANav Server:
nav to <dest>
: begin navigation to the named destination within the region
nav dir
: shows a directory of all navigation destinations within the region
nav info <dest>
: show details about a specific navigation destination within the region
nav conf <...>
: send a command to the ANav server
The navigation system allows the unit to automatically move to a target place or object. This is accomplished mainly by walking using a mixture of direct movement and SL pathfinding, although the tp/warp/jump command will teleport the unit directly.
Importantly,
nav follow
is not merely a reimplementation of typical leashing behavior. The unit may hesitate or walk around obstacles, and will often lag behind. This is more akin to the AI of a non-player character in a role-playing game.
To navigate to a named destination, the region must have a navigation server that provides a list of named destinations and their coordinates. This is intended for roleplay.
In Companion, the module
_navigator
performed many of the tasks of ARES nav
. Its 'navigate' feature moved the unit between physical waypoints that triggered events, like a scripted tour guide. This has has no direct equivalent in ARES.
Settings
The
nav
command uses the following database settings (see db). Defaults for these settings are defined in default.db
.
nav.blocked
(default 0): set to 1 when exposed to strong radiation
nav.bookmark
: a key-value store containing bookmark names and locations (as SLURL fragments)
nav.follow.range
(default 2): the range at which to follow the target
nav.follow.target
(only defined when relevant): the key being followed
nav.carrier
(only defined when relevant): the key carrying the avatar (using handles; not directly part of nav
)
nav.speed
(default 6): the speed at which the unit seeks its target or the next waypoint
nav.marker
(default 1): set to 1 to display navigation destination markers on the HUD
Note: Most values from the settings database are not automatically applied after modification. Affected programs must be restarted (e.g. with
@reset
) to update values and apply changes.