4 — Discovered by player
Satisfied when the tagged object is first uncovered for the local player, and again when the object is destroyed by an attacker.
Editor data
- Numeric ID
4- Engine ID
TEVENT_DISCOVERED- Editor name
- Discovered by player
- Need token
NEED_NONE- Parameters
- None
- Attachment
- cell or object
INI example
[Events]
<TriggerID>=1,4,0,0The two offers
Section titled “The two offers”The reveal offer is made as the object comes out from under the shroud, under all of:
- the house it is being revealed to is the local player;
- the object has not already been revealed to that player;
- the object is not owned by the local player;
- the scenario is no longer being set up;
- the object carries a tag.
The death offer is made where the game records the object’s kill, under all of:
- the object is still active;
- it carries a tag;
- the kill has an attacker to credit.
Nothing in the second offer looks at discovery at all. It sits beside the offers for the attacked and destroyed events, which are made from the same place and under the same terms.
Caveats
- The reveal offer is made only for an object the local player does not own, and only the first time that player uncovers it. An object the player already owns never announces its own discovery.
- The offer is made on the machine whose own player uncovered the object, so in a multiplayer game the trigger and its actions run on that machine alone.
- Nothing is offered while the scenario is still being set up, and an object marked as discovered during setup is never revealed a second time. A tag on an object standing inside the player's opening view therefore never receives the reveal offer at all.
- Recording an object's death offers the same event a second time, whenever the object had an attacker to credit the kill to. That offer carries no test of ownership and no test of discovery, so a tagged object of any house springs the event by being destroyed.
- The event may be placed on a map cell as well as on an object, and no offer is ever made to a cell. A tag carrying only this event and riding only on a cell is never satisfied.
- The event describes a moment, so a persistent trigger marks it off the first time it arrives and treats it as satisfied from then on.