TAGGED_PATH

Usage:
TAGGED_PATH <Name>

Description:
Used for defining a path which a monster with the "PATH_FOLLOW" action in its states will follow.

Details:
<Name> references the name of another radius trigger script. This allows us to "daisy chain" the path nodes together.

Use the NAME command to name your radius triggers, then use the TAGGED_PATH property to create a path for a monster to follow. This is similar to how Quake makes monsters follow a path before they encounter the player.

All monsters spawned in a TAGGED_PATH script will be able to follow the path. Use the SPAWN_THING command to spawn the monster you want to walk the path in the first radius trigger script (using TAGGED_IMMEDIATE too), the monster will start here and then follow the path based on the TAGGED_PATH names.

You must use the "PATH_FOLLOW" action in the monster's states in THINGS.DDF (normally the IDLE states). This action makes the monster follow the path. (See DDF Online/THINGS.DDF for more info)

To make a looping path, the last radius trigger should use TAGGED_PATH with the name of the first node. Omitting the last TAGGED_PATH means that the monster will stop there.

NOTE: it's best to make the radius of this trigger about 10, otherwise the monster following the path will starting moving to the next node as soon as it hits the outer radius. Making the radius a small area forces the monster along a more precise path.

Example:

START_MAP map01

  RADIUS_TRIGGER 0 0 10
    NAME walk_1
    TAGGED_PATH walk_2

    TAGGED_IMMEDIATE
    SPAWN_THING imp
  END_RADIUS_TRIGGER

  RADIUS_TRIGGER 150 200 10
    NAME walk_2
    TAGGED_PATH walk_3
  END_RADIUS_TRIGGER

  RADIUS_TRIGGER 300 0 10
    NAME walk_3
    TAGGED_PATH walk_1
  END_RADIUS_TRIGGER

END_MAP