Introduction

The TriggerSequence Editor configures a TriggerSequence function entity: an ordered list of other entities to fire, optional delays between them, and the start / finished method names that become pins on the flowgraph node.

Entity parameters such as trigger_mode, use_random_intervals, and interval_multiplier stay in the Entity Inspector. This editor only edits the sequence list and method entries stored on the entity.

Opening the Editor

  1. Select a TriggerSequence entity in the composite list or flowgraph.
  2. In the Entity Inspector, click Function.
  3. The TriggerSequence Editor opens, titled with that entity’s name.

Edits apply directly to the selected entity while the window is open. The window closes if you reload commands, select a different entity, or switch composite.

Layout

The window is split horizontally:

  • Entities (top) — ordered targets the sequence will trigger, each with a delay.
  • Triggers (bottom) — named methods this sequence supports (start → finished pairs). These apply to every entity in the list above.

Drag the splitter between the panels to resize. Close is in the bottom-right corner.

Entities

The Entities list shows each sequence entry as a row: the resolved entity hierarchy path, and the delay in seconds. Checkboxes on the left are used for bulk removal.

Click Add Entities… to open the hierarchy picker with checkboxes. Check one or more function entities (you can still follow into nested composites first), then confirm. All checked entities are inserted after the current selection (or at the end if nothing is selected). If nothing is checked, the highlighted row alone is added.

Selected Entity Details

Selecting a row shows the details panel:

  • Entity To Trigger — read-only resolved path. Use Select New to repoint this entry at a different function entity (single pick). Use Go To to jump the main editor to that entity (this closes the TriggerSequence Editor after confirmation). These actions require a single selected row.
  • Time To Wait Before Triggering (In Seconds) — delay for the selection. With multiple rows selected (Ctrl/Shift+click), the same delay is applied to all of them. If selected delays differ, the field starts blank until you enter a value. Only numeric values are accepted.

Reorder & Remove

  • Drag a row in the Entities list to reorder it (insertion mark shows where it will land). Up / down buttons still work as an alternative.
  • Sequence order is the firing order (subject to the entity’s trigger_mode and related parameters).
  • Check one or more rows and click Remove Checked to delete them after confirmation.
  • There is no single-row delete button for entities; use checkboxes + Remove Checked.

Triggers

The Triggers list is the set of start / end parameters this TriggerSequence exposes. Each line shows method -> method_finished.

These methods apply to all entities in the Entities list — when the sequence runs a method, every target is triggered with that method name (with its own delay).

  • Add New Trigger — inserts a method entry using the name currently in the Parameter field (or an empty name if the field is blank). Inserts after the selection, or at the end.
  • Delete Selected Trigger — removes the selected method entry.
  • Select a trigger to edit its Parameter To Trigger name, then click Save to apply. Saving regenerates the related relay / finished names from that parameter string.

Method Pins

For a parameter name X, the editor stores three related identifiers that appear as pins on the flowgraph node:

  • X — input method (start)
  • X_relay — relay output
  • X_finished — finished output

After adding or renaming methods, refresh or reselect the node on the flowgraph if pin lists look stale. Standard methods like proxy_enable / proxy_disable remain on the entity type itself; the Triggers list is for the extra sequence methods you define here.

Closing

Click Close to leave the editor. Before closing, OpenCAGE checks that every sequence entry points at a real entity hierarchy. If any entry is empty or incomplete, you get an error and the window stays open so you can fix it.

There is no separate Save button — sequence and method edits are already on the entity. Persist them with the usual composite / level save.