Skip to content
OpenTS Manual

7 — Reinforcement (team)...

Builds one team of the type named and delivers it onto the map, ready to follow its script.

Editor data
Numeric ID
7
Engine ID
TACTION_REINFORCEMENTS
Editor name
Reinforcement (team)...
Need token
NEED_TEAM
Parameters
  1. Teamteam
Attachment
none
INI example
[Actions]
<TriggerID>=1,7,1,<Team>,0,0,0,0,

How the group arrives

Section titled “How the group arrives”

The members are created as the scenario’s own objects are, so nothing is produced, nothing is paid for and the delivery does not wait on a factory. They are gathered into one team, given the veterancy the team type asks for, and filled to capacity where the type says so; anything with room for passengers takes the rest of the group aboard.

Four deliveries are possible, and the group’s own composition picks between them.

  • A drop pod team of infantry alone falls onto the destination cell.
  • A group whose every member burrows arrives underground and surfaces at the destination.
  • A group of infantry alone walks out of a structure or transport standing at or beside the destination, where there is one to walk out of.
  • Anything else enters at the calculated cell on the receiving house’s Edge and drives, walks or flies in from there.

A dropship load is a case of its own, and StartingDropships owns what it carries and what goes wrong when the receiving house is not the player’s.

Caveats
  • The team belongs to the house its own type names, not to the house that owns the trigger, and it is that house's edge and that type's waypoint the delivery works from.
  • A team type whose script carries no missions has an attack-waypoint mission written into that script, which stays there for every later team built on the same script.
  • The arrival is announced, and the cell it arrived at becomes the one the center-on-radar-event command jumps to, only while the receiving house is an ally of the player at this machine and at least one member was placed.
  • Members that cannot be given a legal arrival cell are destroyed rather than left waiting.
  • A task force naming a dropship and nothing else is delivered as a dropship load instead, for the first three such deliveries a house makes. The fourth and later ones deliver the empty dropship.
  • The dropship type is looked up by the fixed name DSHP on every reinforcement, and the result is used without being checked, so a rules tree that registers no such aircraft reads one position before the start of the aircraft list each time either reinforcement action runs.