Skip to content

8 — Any Event

Satisfied by every offer, so a trigger with no other event fires as soon as it is enabled.

Editor data
Numeric ID
8
Engine ID
TEVENT_ANY
Editor name
Any Event
Need token
NEED_NONE
Parameters
None
Attachment
cell, object, map, house or general
INI example
[Events]
<TriggerID>=1,8,0,0

Any Event is satisfied by every offer. It is a standing event with no condition, so the naming requirement that decides most events does not apply to it, and nothing else is tested.

A trigger whose only event is Any Event fires on the first offer it receives while enabled. Its tag is on the general list, which makes offers at the start of each logic frame, and on its house’s list, which makes offers later in the same frame. A trigger that is enabled when the scenario starts therefore normally fires during the first frame. A trigger enabled later by another trigger fires on its next offer from either list. A pass over a list can skip a tag when the tag listed before it is destroyed by firing, as Where a tag is offered an event describes.

Any Event permits all five attachments, so its tag gets all five whatever the trigger’s other events permit. When the scenario starts, the tag joins the general list, the zone list and the list of the house that owns its trigger. The map may also place the tag on an object or a cell.

The general list and the house list each offer the tag something every frame, and the trigger’s other events are examined on offers from both. The zone list makes offers only to tags whose triggers include zone entry, and a zone-entry event puts its tag on that list by itself. Joining it through Any Event therefore changes nothing.

A semi-persistent tag counts only the objects and cells that hold it, and joining a list adds nothing to that count. Pairing Any Event with another event therefore does not make a semi-persistent tag fire when the tag rides on no object or cell.

Caveats
  • Adding it to a trigger with other events does not change what those events require, because every event on a trigger must be satisfied. It does add the offers described under [Where the tag ends up](#where-the-tag-ends-up).
  • Avoid a persistent tag. If the tag is first on its house's list, the trigger fires on every offer, which is usually twice every frame, once from each list. Otherwise the house list offers the tag again each time it fires. For as long as the trigger stays enabled and satisfied, it then fires without end within one frame and the game hangs.