= WaitForTrigger ? <kuid2:57344:80001:3>
Does what it says, it waits for a trigger to be activated somewhere on the route. Most often it is used in a manner similar to the other wait commands but in this case it waits for the trigger. The command is pretty "dumb" in that it just interrupts the processing of driver commands until the trigger is activated. Skillful programming of the trigger can let you do some neat things. An example of its use would be to have a AI train waiting for a meet just out of sight until the players train takes the siding and trips the trigger which would allow the AI train to approach and pass the player's train on the mainline.
= WaitUntil ? <kuid:41009:900005>
This causes a train to wait until a certain time is reached on the game clock. For example: wait until 10:35 am. When the clock reaches the set time the command is completed.
= Wait Until Minute ? <kuid:178892:80003>
Same as above but different author. This command only reads the minutes on the clock so it can be used to make something wait say 10 minutes after the hour of any hour.
=ReleaseJunction ? <kuid:131986:210012>
Description:
A driver command that lets a driver to release the junction he/she has been holding (using the WaitForJunctionPermit command). This command along with
WaitForJunctionPermi command help eliminate the fight between the drivers taking the same
long single track line (with branches) to move from one station (Station A) to another
(Station B). Here is how these commands work: (1) Create a (dummy) junction that is disconnected from the main rail network between Stations A and B, for example.
(2) Give the dummy junction a unique name such as PathAtoB. (3) For all drivers stationed at both ends of PathAtoB, use WaitForJunctionPermit command to ask permissions to hold junction PathAtoB. Make sure that you choose junction PathAtoB in the menu. (4) Use this command to release the junction as soon as the driver, one at a time reach their desired destination on the opposite ends. Also, make sure that you choose the correcth junction (junction PathAtoB) using this command. With this command along with ReleaseJunction command, the drivers waiting on both ends of a path are given permissions in the order in which the permissions are requested. Thus only one driver at a time can use the entire path before a second driver is given permission. Note that using this command for a regular junction in the rail network may result in unexpected behavior. Use this command to release dummy junctions.
= Path Command ? <kuid2:71155:60007:4>
Description:
The path rule extends the routing of trains in TRS. It allows the definition of user defined paths which can be set by a driver command.
This command is used in driver sessions to set paths for a train. Due to limitations in TRS it is not possible to use paths in conjunction with the builtin driver commands. You should use the autopilot command instead.
For more information about the path rule and how to use the command in your sessions, see
http://www.mutton.de/trainz/pathrule
= pantz ? <kuid66277:80004>
Raises or lowers the pantagraph on electric locos with operating pantagraphs.
= notify (built-in)
Sends a message to the console message panel in Driver. The same place you look to see the message when your driver icon has a red ! over it. Most often used to signal that a AI train has reached a destination.
= Hornz <kuid:66277:80001> will blow the horn with this command.
Blows the horn.
= Change Destination Sign ? <kuid2:208616:99003:1>
DriverCommand to change the destination sign of vehicles, designed to use this command. Passenger trains outside of the US often have signs on the front of the lead loco that indicates where the train is traveling to so that passengers at stations will know what train to get on. Same concept as buses use. This command has limited use since it requires a loco which has changeable signs.
And before you ask:
Autopilot Command:
Description:
This command sets the train to autopilot mode. The driver will obey all signals but doesn't change junctions. It is the user's responsibility to set the correct path. To use the command it must be added to the Driver Command Rule in Surveyor.
The command has two options:
- activate:
Activates the autopilot on a train. The train runs forever, the only way to stop it is to abort the command.
- stop at trackmark:
The train drives until it reaches a selectable trackmark. When the trackmark is reached the next command is executed (or the train is stopped).
When the command is used in conjunction with the autopilot rule it is possible for drivers to leave trains which have autopilot enabled. The rule will remember the state of the autopilot even on unattended trains and keeps them running. If a driver returns to an autopilot train the command is added to the schedule again.
William
