Skip to content
OpenTS Manual

2 — Spied upon

Never fires. No part of the game announces this event, so a trigger waiting on it is never satisfied.

Editor data
Numeric ID
2
Engine ID
TEVENT_SPIED
Editor name
Spied upon
Need token
NEED_NONE
Parameters
None
Attachment
object
INI example
[Events]
<TriggerID>=1,2,0,0

What a structure’s tag is offered instead

Section titled “What a structure’s tag is offered instead”

An infantry that reaches the structure it was sent at offers that structure’s tag Entered by…, before anything about the soldier is examined. That is the one offer an infiltration produces, and it names the wrong event: a Spied upon event riding on the same tag is rejected in the very offer that reports the arrival.

What follows the offer belongs to the soldier’s flags rather than to the structure’s tag. An Agent=yes soldier records the infiltrating house against the structure and springs nothing further. The event is only attachable to an object, so there is no second place its trigger could be waiting.

Caveats
  • The event describes a moment rather than a lasting condition, and nothing anywhere announces it. Every offer a tagged object receives names some other event, and this one is rejected before its own test is reached.
  • The event carries no test of its own beyond that rejection, so an offer naming it would satisfy it on the spot, whatever the structure and whoever walked in.
  • A trigger that pairs this event with events that do work never fires either, because every event on a trigger has to be satisfied in one offer.
  • 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.