Driver Command Rule: Difference between revisions
From TrainzOnline
Jump to navigationJump to search
m Pw3r moved page Driver Commands Rule to Driver Command Rule without leaving a redirect |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
The Driver Command rule determines the set of commands available to all the drivers in a session. | |||
This rule doesn't wait for anything or execute any child rules. Once started it sets the availability of driver commands according to it's configuration and completes immediately. It is intended to be used as an initialization rule which is run as the session starts. | |||
Commands made globally available in the Driver Command Rule can be disabled and re-enabled for any specific train during the session using the [[Enable/Disable Driver Commands Rule]]. | |||
[[File:DriverCommand.jpg]] | |||
[[Category:Rules]] | [[Category:Rules]] | ||
Latest revision as of 14:13, 12 February 2013
The Driver Command rule determines the set of commands available to all the drivers in a session.
This rule doesn't wait for anything or execute any child rules. Once started it sets the availability of driver commands according to it's configuration and completes immediately. It is intended to be used as an initialization rule which is run as the session starts.
Commands made globally available in the Driver Command Rule can be disabled and re-enabled for any specific train during the session using the Enable/Disable Driver Commands Rule.
