Skip to content
OpenTS Manual

18 — Change team...

Builds a team of another TeamType from this team's members and disbands this one.

Editor data
Numeric ID
18
Engine ID
TMISSION_TEAMCHANGE
Editor name
Change team...
Need token
NEED_TEAM
Parameters
  1. Teamteam

What moves and what does not

Section titled “What moves and what does not”

Members are handed over one at a time. Each is taken out of the old team first and then offered to the new one, which applies the same tests as recruitment. A member is refused under any of:

  • its type does not appear in the new TeamType’s TaskForce;
  • the new TaskForce already holds as many of that type as it asks for, so a team of six changing to a type that wants three keeps three and releases the rest;
  • it is dead, inactive, or in limbo, which a passenger aboard a transport is;
  • it is in radio contact, which covers a member in the middle of loading or unloading;
  • its current mission is not one a team may recruit from;
  • it is not recruitable by a team of the new TeamType’s autocreate setting.

A refused member is not put back. It has already left the old team, so it is released outright and reverts to its own idle behavior. Where the new TaskForce lists nothing the old team was holding, the change produces an empty team and scatters the whole roster.

A member that does move across gives up the tag the old TeamType attached to it, for a house under computer control, and picks up the new TeamType’s tag where the new type names one.

What the new team is

Section titled “What the new team is”

The new team is created from scratch: a fresh copy of the new TeamType’s Script rewound to before its first line, a new tag where the type names one, and the origin its Waypoint sets as its opening center. It is created stopped and under strength, so the ordinary reform delay applies before it takes its first line, and it is subject to the new TeamType’s own Reinforce and Priority from that moment.

Valid values

  • A TeamType the scenario declares. A team is created from it even where nothing can be moved into it.
Caveats
  • The new team belongs to the house that owned the old one, whatever house the new TeamType names. Everything the new TeamType decides for itself is taken from the type, but the ownership is inherited.
  • A member the new TaskForce does not list is not carried over. It is taken out of the old team all the same and left standing where it was, on no team at all.
  • The new team starts stopped and under strength however many members it received, so it gathers and starts from the top of its new Script rather than continuing.
  • The line is the last thing the old team does. Its disbanding records an outcome against every AI trigger that names its TeamType first, and that outcome is a failure unless the old script had reached Success.