Skip to content
OpenTS Manual

19 — Build Building Type...

Satisfied while the named structure is the last one registered against the trigger's own house, which production and first sight both do.

Editor data
Numeric ID
19
Engine ID
TEVENT_BUILD
Editor name
Build Building Type...
Need token
NEED_STRUCTURE
Parameters
  1. Building typebuilding-type
Attachment
house
INI example
[Events]
<TriggerID>=1,19,0,<Building type>

What registers a structure

Section titled “What registers a structure”

Two separate paths write the record the event reads, and only one of them is production.

A structure finished by a factory registers its type against the house that built it, which is the behavior the event’s name describes. A structure also registers its type the first time it is revealed to the local player, and that path does not care where the structure came from or who owns it — the record written is the owner’s. Uncovering an enemy base therefore writes that enemy house’s record, one structure at a time, in the order the player finds them. The only reveals that register nothing are the ones that happen while the scenario is still being set up, which covers the structures standing inside the player’s opening view before the first frame.

The record survives whatever satisfied it. Because nothing clears it, a trigger built on this event goes on being satisfied until its house registers some other structure type, and a persistent tag carrying it fires on every offer over that whole stretch. Watching for a structure the house owns, rather than for the last one it registered, is what Building exists… does instead.

Valid values

  • A BuildingType. The record holds one type at a time, so the comparison is against the most recent registration and not against a list of everything built.
Caveats
  • The record is never cleared. Once the house registers the named type the event stays satisfied until the house registers a different structure type, which may be a long time later or never.
  • Registration is not confined to production. A structure of that house registers its type the first time it comes out from under the shroud for the local player, so scouting an enemy base writes the enemy house's record for it.
  • Reveals that happen while the scenario is still being set up register nothing, so the structures already inside the player's opening view are the one group this path leaves out.
  • Because the second path turns on one machine's vision, two machines in a multiplayer game need not agree about which structure type a house last registered.
  • This is one of the four events exempt from the requirement that an offer name them, which is why an offer about anything at all can satisfy it.
  • The event has nothing to ride on. Its tag joins the list of the trigger's own house, which adds nothing to the attachment total a semi-persistent tag waits on, so a trigger built on events of this kind needs a volatile or a persistent tag.