12 — Destroy Trigger
Changed in 0.1.0
Removes every trigger of the named type from the scenario for good.
Editor data
- Numeric ID
12- Engine ID
TACTION_DESTROY_TRIGGER- Editor name
- Destroy Trigger...
- Need token
NEED_TRIGGER- Parameters
- Trigger
trigger
- Trigger
- Attachment
- none
INI example
[Actions]
<TriggerID>=1,12,2,<Trigger>,0,0,0,0,The tag is left behind
Section titled “The tag is left behind”Each trigger unhooks itself from its tag as it is released, moving the tag’s link on to the next trigger in the chain. A tag that carried a single trigger — the ordinary shape — is therefore left naming nothing at all. It stays on whatever it was riding on and springs nothing for the rest of the scenario.
That empty link is what costs a house its victory when the tag was an allow-win tag: the link is where the disposal reads the house to credit, so destroying the triggers first and the tag afterwards gives nothing back.
Valid values
- A trigger type the scenario declares. One trigger is built from it for each tag that carries it, and every one of those is removed.
Caveats
- Each matching trigger stops springing and firing the moment the action runs, but it is not released until the end-of-frame disposal.
- A trigger that names its own type here marks the very trigger whose actions are running. The rest of that action list still runs, because the refusal is tested only as firing begins.
- The tag survives. Only the triggers hanging off it are taken away.
History
- Changed0.1.0In development