|THE MAIN ITEMS|
|---- Executing sub-tasks|
|---- How tasks work|
System Tasks are just the same as any other tasks except they are not triggered directly by what the player types at the command line. In most cases, they are just called by other task actions, or by events. However, there are other ways of triggering them also. The options for triggering a System task are:
- Only if called by event/task - This task will never run unless explicitly called.
- Immediately - This task will run at the start of the game.
- Player enters location - This task will run when the player enters a particular location.
The first option here is the default. Basically this means that the task is never triggered automatically. If you select one of the other options, you can still call the task from an event or other task.
The second option is useful for initialising things at the start of the game. For example, you may want to set variables to random values, place characters randomly within a location group, or ask the player to enter their name, gender and age.
The third option is useful, because it triggers whenever the player enters a particular location. You could override the 'Player Movement' task, but if the location had several entrances then you would need to override each entrance. This task ignores which entrance you came in, and will trigger as soon as you arrive at the specified location.
|System tasks dont use references. If you want to call a task and pass references to it as parameters, then create a general task but use "#" as the first character of the command. Then just list the references it needs to use for its restrictions or actions.|
|<<< General tasks||Main_Page||Executing sub-tasks >>>|