18 — Civilians Evacuated
Never fires. No part of the game announces this event, so a trigger waiting on it is never satisfied.
- Numeric ID
18- Engine ID
TEVENT_EVAC_CIVILIAN- Editor name
- Civilians Evacuated
- Need token
NEED_NONE- Parameters
- None
- Attachment
- house
[Events]
<TriggerID>=1,18,0,0Where the trigger sits and what it is offered
Section titled “Where the trigger sits and what it is offered”The event can only ride on a house, so its trigger is placed on the list the trigger’s own house polls once a frame. That poll names nothing in particular, and an event describing a moment needs an offer that names it. Nothing else offers this event anywhere, so the trigger sits on that list unsatisfied for the whole scenario.
The mark it would read
Section titled “The mark it would read”An aircraft on the Retreat mission that flies outside the playable area deletes each passenger it holds, and marks the house of every passenger that counts as a civilian. The mark is never cleared.
The test reads that mark on the house that owns the trigger, not on the house whose civilian left. A trigger owned by the player, watching for the civilians it has just flown out, would be reading its own mark rather than theirs — so the two houses have to be the same for the test to mean what its name suggests, which puts the trigger on the civilian house.
- The event describes a moment rather than a lasting condition, and nothing anywhere announces it. Every offer its trigger receives names some other event or names nothing in particular, and neither satisfies an event of this kind.
- The mark it tests is set on the evacuated civilian's own house, while the test reads the house that owns the trigger. The two are the same house only where the trigger belongs to the civilians, so the test would answer the wrong question even if an offer reached it.
- Force Trigger runs such a trigger's actions without examining its events at all, and is the only way to get anything out of one.