Skip to content
OpenTS Manual

27 — Global is set...

Satisfied while the named global variable is set.

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

Valid values

  • A global variable number from 0 to 49. The scenario database gives fifty globals their names, and the event names one of them by number.
Caveats
  • The event reads the variable's current state on every offer rather than catching the moment it changed, so it is satisfied for the whole time the variable stays set.
  • A persistent tag carrying it fires on every offer over that stretch, which is once a frame for a tag on the general list.
  • Changing a global one of the trigger's own events names restarts that trigger's countdown, so pairing this event with a time event measures the delay from the change.
  • Globals survive the end of a campaign mission and are handed to the next one, so a global set in an earlier mission is already set when a later mission starts.
  • Naming a number outside the range of the table leaves the answer never filled in, so what the event reports is whatever was left in the place it reads.
  • The event has nothing to ride on. Its tag joins the general list, which adds nothing to the attachment total a semi-persistent tag waits on, so a trigger built on events of this kind needs a volatile or a persistent tag.