How tasks work
From ADRIFT 5 Manual Wiki
| THE MAIN ITEMS | |
|---|---|
| Locations | |
| Objects | |
| Tasks | |
| ---- Specific | |
| ---- General | |
| ---- System | |
| ---- Executing sub-tasks | |
| ---- How tasks work | |
| Characters | |
| Events | |
| Variables | |
| Groups | |
| Properties | |
| Text Overrides | |
| Hints | |
| Synonyms | |
| User functions | |
This is a step-by-step description of how ADRIFT processes a players command and chooses which tasks to run.
It is not meant to be read through start to finish, it is provided as a reference for more advanced ADRIFT uses to help design more complex multiple-task commands and debug problems.
- The first thing the parser does is replace the words "it", "them", "HIM#him" and "HER#her" with the appropriate object or character that the player most recently refered to.
- The parser now checks each general task, starting from the one with the lowest number in the "Task Priority:" field on its "Advanced" page and proceeding in order until it finds a match between the player's input and one of the command lines of a task, using "Advanced Command Construction" matching.
- When it finds a matching general task, it now tries to match the references. Eg.If the command contains an %object% reference then ADRIFT searches through all of the objects in the game trying to find one which matches what the player typed in that part of the input. Note that the player may have entered the names of several objects, eg. "the watch and the pendant" or "all except the hat", and all of these must match objects in the game.
| <<< Executing sub-tasks | Main_Page | Characters >>> |
