| summaryrefslogtreecommitdiff |
diff options
Diffstat (limited to 'content/fate_v1/declarations/events/_index.md')
| -rw-r--r-- | content/fate_v1/declarations/events/_index.md | 18 |
1 files changed, 0 insertions, 18 deletions
diff --git a/content/fate_v1/declarations/events/_index.md b/content/fate_v1/declarations/events/_index.md deleted file mode 100644 index 0c00d52..0000000 --- a/content/fate_v1/declarations/events/_index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Events ---- -Events are how a Fate narrative can communicate to the interpreter that -something which cannot be expressed in Fate needs to be performed. The execution -is paused until the event is resolved by the interpreter. To avoid mistakes, any -event type must be declared before use. - -#### EVENT -{{< fatecode >}}(declare_event_type {string} [C0 = TYPE] ... [CN = TYPE]){{< /fatecode >}} -**Effect:** An event with the name `{string}` and taking parameters of types -`[C0]`, ..., `[CN]` can be used. - -## Examples -* `(declare_event_type user_string_input text (ptr string))` -* `(declare_event_type wait int)` -* `(declare_event_type set_background_to string)` -* `(declare_event_type rumble)` |