Trigger Configuration
Every trigger’s configuration sheet has four tabs: General, Program, Variables, and History. See Program Editor for the Program tab.
General tab
Section titled “General tab”Template, at the top of the tab, applies a saved or example configuration, or saves the current one for reuse. Applying a template overwrites the whole trigger, including its program. See Recipes and Templates.
| Field | What it does |
|---|---|
| Events | The Region events that subscribe this trigger. See Events for the full list. |
| Additional Events | Events outside the system’s own Region events, such as pointer clicks or door state changes. See Events. |
| Restricted To | Limits which triggering users the trigger runs for: everyone, players only, or the GM only. |
| Restricted Tokens | Limits which tokens can fire the trigger, by whether a player owns them. |
| Chance | The percent chance the program runs once every other gate passes. |
| Minimum Required | How many qualifying attempts the trigger needs before its program runs. |
| Cooldown | The minimum time between runs. |
| Once Per Token | Runs at most once for any given token. |
| Requires Vision | Only runs if the triggering token is currently visible. |
| Allow When Paused | Runs even while the game is paused. |
| Trace Tile Image | Shapes the Region to the linked Tile’s image instead of its rectangular bounds. |
| Linked Tile | The Tile this trigger is tied to. See Tiles for how the two stay in sync. |
Minimum Required and Once Per Token both read stored data instead of tracking themselves separately. Minimum Required counts every qualifying attempt on the trigger, not only the ones that would otherwise fire it. Once Per Token checks whether that token already appears in the trigger’s History.
Cooldown counts in the world’s game time, not real time.
If the same trigger fires again while an earlier fire’s run is still going, the new fire queues behind it and runs once the first finishes.
If a run throws an error, the user who fired it sees a notification naming the Region, and the failed run appears in History with the error attached.
Variables tab
Section titled “Variables tab”The Variables tab holds a list of name/value pairs stored on the trigger. They persist across every fire and are readable elsewhere as {{variables.name}}; see Placeholders and Conditions. Adding a name that already exists overwrites its value. Enter a value as JSON; anything that doesn’t parse as JSON is stored as plain text.
History tab
Section titled “History tab”The History tab lists the trigger’s past fires, most recent first, each with the event name, the triggering user, and how long ago it ran. A failed run also shows its error. Each entry has its own delete control that removes just that entry; deleting a token’s entry lets Once Per Token fire for that token again. Reset History clears the log and the Minimum Required attempt counter together.