Skip to content
OpenTS Manual

54 — Enemy In Spotlight... (repeating)

Fires while a sweeping beam on the tagged structure has a non-allied soldier or vehicle inside its detection radius, and refuses to be marked off once it has.

Editor data
Numeric ID
54
Engine ID
TEVENT_ENEMY_IN_SPOTLIGHT_REPEATING
Editor name
Enemy In Spotlight... (repeating)
Need token
NEED_NONE
Parameters
None
Attachment
object
INI example
[Events]
<TriggerID>=1,54,0,0

Enemy In Spotlight… covers what the scan takes and which beams reach it, and all of it applies to this form unchanged. What separates the two is whether a satisfied event is remembered, and this is the form that is not.

The difference shows on a persistent tag whose trigger pairs the event with something else. With the plain form, one intruder settles the spotlight term for the rest of the scenario and the trigger then waits only on its other events. With this form the beam has to have an intruder in view on the very offer that satisfies the last of them.

Caveats
  • The two spotlight events run no test of their own and are sprung together on the same find, so they answer identically to every offer they are given.
  • The one difference is that this form is never marked off as having happened, so it is examined afresh on every later offer while the plain form stays satisfied.
  • Nothing is marked off on a volatile or a semi-persistent tag, so on those two the two forms behave alike and the choice between them changes nothing.