Skip to content
OpenTS Manual

13 — Elapsed Time...

Satisfied when the trigger's countdown reaches zero, the countdown being the given number of seconds.

Editor data
Numeric ID
13
Engine ID
TEVENT_TIME
Editor name
Elapsed Time...
Need token
NEED_NUMBER
Parameters
  1. Numberinteger
Attachment
general
INI example
[Events]
<TriggerID>=1,13,0,<Number>

Valid values

  • A number of seconds. The editor calls these fifteen-frame units, which is the same thing at the engine's logic rate of fifteen frames a second.
Caveats
  • The countdown belongs to the trigger rather than to the event. It restarts when the trigger is created, when it is enabled, when a global or local variable one of the trigger's own events names changes value, and on any offer that satisfies every event of a persistent trigger.
  • A trigger carrying more than one time event keeps only one countdown between them, so the second delay written into the map file has no effect of its own.
  • A trigger that starts disabled has its countdown restarted when something enables it, so the delay runs from the enabling rather than from the start of the scenario.
  • A delay of zero is already expired, so the event is satisfied on the first offer the trigger receives.
  • The general list is offered this event once every frame with no condition attached, which is what makes a tag on that list examined constantly.
  • 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.