5 — Destroy Team...
Disbands every team of the type named and releases the members into their own idle behavior.
Editor data
- Numeric ID
5- Engine ID
TACTION_DESTROY_TEAM- Editor name
- Destroy Team...
- Need token
NEED_TEAM- Parameters
- Team
team
- Team
- Attachment
- none
INI example
[Actions]
<TriggerID>=1,5,1,<Team>,0,0,0,0,The track record owns how an outcome moves a trigger’s weight, and it is keyed on the TeamType alone: it does not ask which trigger raised the team or which house owned it, so disbanding a scenario-placed team of a type an AI trigger also names moves that trigger’s record just the same.
Valid values
- A TeamType the scenario declares. A line naming no team runs and does nothing.
Caveats
- Every team of the type goes, whichever way it came about — placed by the scenario, raised by an AI trigger, or created by the create-team action.
- Each member is released into its own idle behavior rather than carrying on with the script. A soldier or vehicle falls back on guarding, a harvester returns to harvesting, and the mission the script had it running is abandoned.
- A member of a computer house also has the team's own tag taken off it, so a trigger riding on that tag is no longer offered anything through that object.
- Disbanding is recorded against the AI triggers. Every trigger that names the type as its first team is credited with the outcome, which is a failure unless the team had already reached the Success mission in its script, and a failure lowers the weight that trigger is drawn with for the rest of the scenario.