TOTS Dev

Dev Page

Event-driven story scripting

How to get Started

An event file defines a list of events, each containing a series of executable in-game actions. Our task is to ensure each event triggers at the right moment and executes all its associated actions.

How events work

An event consists of three components: Trigger, Conditions, and Actions. The execution sequence is as follows:

1. One of the event's Triggers is activated by the game.
2. The event then evaluates all Conditions. Only if every condition passes:
3. The event sequentially executes all Actions.

Example:

1. The player presses the K key on the keyboard (Trigger).

2. The event checks:

   • Is a specific character still alive?
   • Does the character have enough energy?
   • Is a certain location currently unoccupied?

3. If all checks pass, it executes:

   • Move the character to a target position.
   • Play a cool animation at the character's location.
   • Wait for 3 seconds.
   • Make the character deliver a line of dialogue.

What if a event without any trigger

When an event has no trigger defined, it will automatically execute every game frame until all conditions are met, then perform its actions.

You can disable this auto-trigger behavior. When disabled: * The event will never trigger automatically * It can only be activated manually through another event's "Trigger Event" action

Repeat an event

An event can be configured with: * Maximum repeat count - Limits how many times the event can be triggered * Minimum interval - Specifies the required delay between consecutive triggers