Running Triggers

The Manual handler

Every trigger’s Program tab includes a Manual handler alongside the handlers for its subscribed events. Build a program under Manual for anything you want to run on demand instead of in response to an event. Every way of running a trigger on demand below runs its Manual handler, unless it says otherwise.

Running from the Tile HUD

Linking an enabled trigger with a Manual handler to a Tile adds a Run Trigger power button to that Tile’s HUD. Clicking it runs the Manual handler of every such trigger linked to the Tile, passing along whichever token is currently selected on the canvas. See Tiles for linking a trigger to a Tile.

@Trigger links

Typing @Trigger[uuid]{Label} into a journal page or chat message renders a clickable link that runs the named trigger’s Manual handler when clicked. Label is optional; without it the link shows the trigger behavior’s name.

To get a trigger’s UUID, open its configuration sheet and click the Copy Document UUID button in the window’s header, then paste the result into the @Trigger[uuid]{Label} text.

Show Dialog buttons

The Show Dialog action can pop up a dialog with its own buttons, each naming a handler to run when clicked. If the dialog’s content includes form fields, their values reach that handler as top-level {{path}} placeholders, the same way an event’s own data does. See Placeholders and Conditions. Dismissing the dialog without clicking a button runs the On Close handler instead, if one is set.

Trigger Another Region

The Trigger Another Region action runs another trigger for the same event this program is handling. If the target has no handler for that event, it runs the target’s Manual handler, or its only handler if just one is configured.

Stop Remaining Actions

Stop Remaining Actions can name another trigger instead of stopping the run it’s in, halting that trigger’s run at its next action.

Running from a macro

Call GLYPH.runTrigger(behaviorUuid, handler, data) from a macro to run a trigger’s handler the same way a Tile button or journal link does. See Developers for the full signature and what data can carry.

await GLYPH.runTrigger('Scene.<sceneId>.Region.<regionId>.RegionBehavior.<behaviorId>');

Gates still apply

A Manual run, a Tile button, a journal link, a dialog button, and a macro call all pass through the same gates as an event-triggered run: restrictions, cooldown, Once Per Token, and the rest. A run also always happens on the Primary GM’s client; requesting one from another client, including a player’s, relays it there. With no GM connected, nothing runs.