21 — Build Infantry Type...
Satisfied while the named infantry is the last one the trigger's own house finished producing.
Editor data
- Numeric ID
21- Engine ID
TEVENT_BUILD_INFANTRY- Editor name
- Build Infantry Type...
- Need token
NEED_INFANTRY- Parameters
- Infantry type
infantry-type
- Infantry type
- Attachment
- house
INI example
[Events]
<TriggerID>=1,21,0,<Infantry type>Valid values
- An InfantryType. The record holds one type at a time, so the comparison is against the most recently finished soldier and not against a list of everything built.
Caveats
- The record is never cleared. Once the house finishes the named infantry the event stays satisfied until the house finishes infantry of a different type, so a trigger on it catches a stretch of time rather than a moment.
- Only the production path writes the record, so infantry that reaches the house any other way leaves it as it was.
- 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 describes a lasting condition once the record is written, so a persistent tag carrying it fires on every offer until the record changes.
- 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.