Skip to content

33 — Selected by player

Satisfied when the tagged object goes from unselected to selected under the local player's own control.

Editor data
Numeric ID
33
Engine ID
TEVENT_SELECTED
Editor name
Selected by player
Need token
NEED_NONE
Parameters
None
Attachment
object
INI example
[Events]
<TriggerID>=1,33,0,0

The offer is made under all of, in this order:

  • the object is not in limbo, is not already selected, and is of a type that may be selected;
  • it is not a loaner, meaning an object the scenario lends the player rather than gives;
  • no structure is waiting to be placed on the map;
  • the house that owns the object is under the local player’s control;
  • the selection voice switch is on.

The last two are what make the event a single-player one. A computer house’s object never springs it, and an object of another human player’s house never springs it on this machine.

Caveats
  • The offer is made only for an object whose house the local player controls, and only on that player's own machine, so the trigger and its actions run on that machine alone.
  • The offer rides on the same switch as the spoken selection response. Selecting several objects at once turns that switch off after the first of them, so a band box or a group hotkey springs the event for one object and for no other.
  • A band box or a group hotkey leaves the switch off afterwards. Until something turns it back on — issuing an order to the current selection does — a later single selection springs nothing either.
  • Adding an already selected object to the selection is not a selection, so re-clicking a selected object offers nothing. The object has to be unselected first.
  • An object of a type that cannot be selected, an object in limbo, a loaned object, and any object at all while a structure is waiting to be placed, are refused before the offer would be made.
  • 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.