Skip to content

35 — Enemy In Spotlight...

Fires while a sweeping beam on the tagged structure has a non-allied soldier or vehicle inside its detection radius.

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

A beam runs the scan once per frame and springs the event under all of:

That radius grows as the beam swings away from the structure, so the same nine cells are searched throughout but the distance the intruder is allowed to stand at is not fixed.

The beam’s behavior decides whether the scan is reached at all. A sweeping beam runs it every frame. A circling beam and a beam held still never do, so switching a beam to either silences the event for as long as it stays there.

A following beam runs the scan on the one frame it loses its target and drops back to sweeping. On that frame the beam’s position is written back from a figure the follow path never worked out, so where the scan looks is not settled by where the beam had been.

Caveats
  • The scan is run from where the beam is standing rather than from the structure, and the beam travels well away from it.
  • Soldiers and vehicles are the only intruders counted. An aircraft, a structure or anything else standing in the light is passed over.
  • The test is alliance, not hostility. A neutral or a civilian object the structure's house has not allied itself with counts as an intruder.
  • Both spotlight events are sprung on the same find, one immediately after the other, so nothing in the offer distinguishes them.
  • The tag has to be on the structure carrying the beam. A tag on the intruder, or on the cell the beam is over, is offered nothing.