Skip to content
OpenTS Manual

46 — Ambient light >= ...

Satisfied while the scenario's ambient light is at or above the given percentage of full daylight.

Editor data
Numeric ID
46
Engine ID
TEVENT_AMBIENT_GREATER_THAN
Editor name
Ambient light >= ...
Need token
NEED_NUMBER
Parameters
  1. Numberinteger
Attachment
general
INI example
[Events]
<TriggerID>=1,46,0,<Number>

Valid values

  • A percentage, where 100 is the light level a map writes as Ambient=1. The comparison is at or above the number, as the event's name says and not as its description does.
Caveats
  • Most maps sit at 100 or thereabouts, so a number of 100 or less is satisfied from the first frame and stays that way until something darkens the scenario.
  • The reading is the level in force at that instant, which is not the map's declared level while the light is on its way to a new target. It slides toward the target one step at a time, and both the step and the interval come from the rules.
  • An ion storm is what moves the level in an ordinary scenario, taking it to the map's storm level while the storm runs and back afterwards. The ambient light actions move it directly.
  • The event describes a lasting condition, so a persistent tag carrying it fires on every offer for as long as the light stays that high.
  • 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.