This module is used to specify the teams used in the match and what their attributes are. Matches without teams can be setup with the players module.
The soft player limit for each team is set with the
max="" attribute and the hard limit with
max-overfill. If max overfill is not explicitly defined the default will be set to 25% over the maximum team size. Players will not be able to join teams once the max overfill team size is reached.
The team's name is specified inside the
<team> element. The name should be kept as short as possible and not contain "Team", for example, "Azure" and not "Azure Team".
plural attribute specifies if the team name is plural, e.g. "Attackers"; PGM will use this to pick appropriate win messages, etc. The
show-name-tags attribute specifies who can see player name tags, this only applies to players, observers will always see all name tags.
It is common for maps to only have 2 teams, although more are possible it usually just causes confusion.
|The teams node, containing all the individual teams.|
|A single team node containing the teams name.||String|
|Unique identifier used to reference teams from other places in the XML.||String|
|The team's display color.||Chat Color Name|
|The color of a player's name tag on this team.||Chat Color Name|
|The team's name is plural, used in status messages.|
e.g., instead of
|Specify who can see the name tags of players in this team.|
Accepts:, , or
|Required amount of players for this team.||Number|
|Maximum players for this team, normal players cannot join the team once it reaches this size.|
Premium players may join over this limit until is reached.
|Maximum players hard limit for this team, nobody can join the team once this limit is reached.|
Must be greater than the defined .
The total maximum number of players in the example given above is 100, however, the max overfill will allow up to 140 players. Servers currently have a player limit of 150, so 100 players in total would allow 50 observers, or 10 observers if teams are at max overfill.