49
edits
→Details
(Created page with "{{dev/uicvar}} Path for the startup script file. <kua>set startup 'startup.cfg' </kua> == Arguments == * name - 'startup' * value - Relative asset path for the startup script file. Default value is unset. == Associations == * Is by default placed in the 'global' context. == Details == Set a script file to be run just after basic engine systems are started. If no value is set, no startup script will be run. The similar config script, 'config.cfg', file is run after ba...") |
|||
| Line 11: | Line 11: | ||
== Details == | == Details == | ||
Set a script file to be run | Set a script file to be run after basic engine systems are started. If no value is set, no startup script will be run. | ||
The similar config script | The similar engine config script 'config.cfg' file is run after basic module initialization. The config file is a place where the startup script can be set. | ||
Startup stages: | Startup stages: | ||
* Process load | * Process load | ||
* | * Modules initialization | ||
** Commands and variables with default values are created | ** Commands and variables with default values are created | ||
* Config script is run | * Config script is run 'config.cfg' | ||
* | * Modules start | ||
** Use of default or config set variables or other changes | ** Use of default or config set variables or other changes | ||
* | * '''Startup script is run 'startup.cfg'''' | ||
* Server module load | * Server module load | ||
* Engine | * Engine run | ||
=== Using === | |||
For example, the 'map' and 'module' load defaults can be unset, and then no map or module will be loaded. The setup script can then be used to provide a more sophisticated configuration. This includes choosing which services are inittially started, and so on. | |||
== Examples == | == Examples == | ||