Skip to content
OpenTS Manual

28 — Global is clear...

Satisfied while the named global variable is clear.

Editor data
Numeric ID
28
Engine ID
TEVENT_GLOBAL_CLEAR
Editor name
Global is clear...
Need token
NEED_GLOBAL
Parameters
  1. Global variableglobal-variable
Attachment
general
INI example
[Events]
<TriggerID>=1,28,0,<Global variable>

Valid values

  • A global variable number from 0 to 49. The rules file can name each number in its [VariableNames] section, but the event stores only the number.
Caveats
  • Globals start each mission clear, except those carried in from an earlier campaign mission or set by a campaign launch file. An enabled trigger holding only this event therefore usually fires on the first frame. [What survives the boundary](/systems/campaign-progression/#what-survives-the-boundary) covers the carried globals.
  • The event tests the variable's current state, not the moment it changed, so it is satisfied for as long as the variable stays clear. A persistent trigger holding only this event fires every frame during that time.
  • When a global changes, every trigger with an event naming it restarts its elapsed-time countdown. Pairing this event with an elapsed-time event therefore measures the delay from the change.
  • Keep the number between 0 and 49. For any other number, the result of the test is unpredictable.
  • Give the trigger a volatile or a persistent tag. This event puts its tag only on the general list, which does not count toward the attachments a [semi-persistent tag](/systems/trigger-springing/#tag-lifetimes) waits on. A semi-persistent tag therefore never fires unless it also rides on an object or a cell.