Skip to content

8 — Any Event

Satisfied by every offer without examining anything, so a trigger carrying it alone fires on the first frame 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

The event describes a lasting condition rather than a moment, which exempts it from the naming requirement that decides most events, and it then carries no further test. Whatever an offer was about, the answer is yes.

A trigger whose only event is this one therefore fires on the first offer that reaches it. The general list is walked at the top of every logic frame and offers elapsed time with no condition attached, so that first offer arrives on the first frame the trigger is enabled — which is what the editor means by springing immediately.

The event permits every one of the five attachments, so it also decides where its tag lives. The tag joins the general list, the zone list and the list of its owning house at once, and the map may place it on an object or a cell as well. The zone list is walked only for tags watching for zone entry, so that placement never produces an offer; the other two both produce one every frame.

That matters for a trigger that pairs this event with a real one. A semi-persistent tag counts objects and cells only, and joining two engine lists adds nothing to that count, so pairing this event with another does not rescue a semi-persistent tag that rides on nothing.

Caveats
  • The event has no test of its own and describes no moment, so it is satisfied whatever the offer was about. It is not that every offer names it; it is that nothing is compared.
  • Adding it to a trigger that already has events makes no difference to whether that trigger fires, because every event on a trigger has to be satisfied anyway.
  • It does change where the tag is placed. It permits all five attachments, so a tag carrying it joins the general list and its house's list whatever the trigger's other events would have asked for, and the trigger's other events are then examined on both.
  • A persistent tag carrying it is offered something from each of those two lists in the same frame, so its trigger fires twice a frame rather than once.