Skip to content
OpenTS Manual

23 — Leaves map (team)...

Satisfied while a team built from the named type has run out of members with its leave-map mark raised.

Editor data
Numeric ID
23
Engine ID
TEVENT_LEAVES_MAP
Editor name
Leaves map (team)...
Need token
NEED_TEAM
Parameters
  1. Teamteam
Attachment
general
INI example
[Events]
<TriggerID>=1,23,1,<Team>

What raises the leave-map mark

Section titled “What raises the leave-map mark”

The mark sits on the team rather than on any of its members, and four things raise it:

  • a team given a mission target in a cell outside the playable area, which also clears every member’s destination;
  • an aircraft that carries team members off the map, which marks the team of each passenger it deletes and the team of the aircraft itself;
  • a vehicle on guard duty that finds itself outside the playfield, which marks its team as it is deleted;
  • any infantry on a team that has ever stood inside the playable area, every frame, whether or not it is anywhere near the edge.

The last of these is why the mark is raised for most teams that contain infantry, and why such a team satisfies the event by being wiped out.

When the offer is made

Section titled “When the offer is made”

Team processing makes the offer at the two points where it disposes of a team that has no members left, and disposal follows immediately in both. The test then scans the live teams for one of the named type that is both empty and marked, and the team making the offer is still there to be found.

Valid values

  • A TeamType the scenario declares. The test looks for a live team of that exact type, so a team of a different type leaving the map satisfies nothing.
Caveats
  • The mark the test reads is raised for every team that holds infantry which has been inside the playable area, on every frame, with no test of the map edge at all. For such a team the event is therefore satisfied when its last member is destroyed, not only when its last member walks off the map.
  • Nothing ever lowers the mark except giving the team a fresh mission target inside the playable area, and the next frame raises it again while infantry remains.
  • An empty team offers the event when it has reached full strength at least once, meaning the number of members its TaskForce asks for. Outside a campaign a team that never filled up offers it too, once it has sat unfilled past the dissolve delay.
  • The offer goes to every tag on the general list, not to a tag connected with the team, and each of those tags then runs the test for the team type its own event names.
  • The event has nothing to ride on. Its tag joins the general list, 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.
  • A trigger owned by a house the scenario does not contain skips the test entirely and is satisfied by the offer alone, whichever team produced it.
  • The event describes a moment, so a persistent trigger marks it off the first time it arrives and treats it as satisfied from then on.