file contains the generic functions used to make people walk the waypoints. The naming of the waypoints is important in order to use these functions:
where ## is a two digit number starting with 01. The NPCtag
portion should match the .utc tag exactly.
(There is a 2nd naming convention that uses wp_xx_## where xx is a two digit number, but this requires extra work with Local Numbers for each creature.)
Now, for generic walkpaths, you only really need one .utw file and then you can use the .git file to spawn it multiple times using different tagnames
(using the naming convention described above). Almost every .git file has an example of this in its WaypointList field.
Your .utc's spawn-in script should be modeled after k_def_spawn01.nss
inasmuch that you preserve the following lines:
These lines will force your .utc to start walking the waypoints that you've named especially for them.
A problem I found was that when you talked to them they stopped walking their waypoints, I had to add the following script to fire onEndDialog to fix it.
// Force them to continue walking waypoints.
Stormtrooper789 says: For random walking you may be able to do without any waypoints. Use the following script:
Attach this to the .utc OnHeartbeat script event.