Skip to content
OpenTS Manual

37 — Local is clear...

Satisfied while the named local variable is clear.

Editor data
Numeric ID
37
Engine ID
TEVENT_LOCAL_CLEAR
Editor name
Local is clear...
Need token
NEED_LOCAL
Parameters
  1. Local variablelocal-variable
Attachment
general
INI example
[Events]
<TriggerID>=1,37,0,<Local variable>

Valid values

  • A local variable number from 0 to 49. The map declares its own locals, giving each a name and optionally a starting state.
Caveats
  • A local declared with a starting state of 0, or with none at all in a scenario that has not run before, is clear on the first frame, so a trigger built on this event alone fires immediately.
  • Locals are not cleared between scenarios. A local the map declares without a starting state keeps whatever the previous mission left in it, so this event is not reliably satisfied at the start of a later campaign mission.
  • 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 clear.
  • 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 local 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.
  • 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.