Team Configuration
teams.yml
As of v0.3.0
Team Layout
teams.yml #1:
RAINBOW: members: - Godness RED: members: - Friend - Fisher - Froyd BLUE: members: - Devil - Daniel GREEN: members: - LoneRanger BLACK: members: - Evil
In the above configuration, Godness is able to teleport to anyone but Evil. The members of RED, BLUE and GREEN are not allowed to teleport to their supergroups' members (Godness). RED's members can only teleport to other members of RED. Evil has no team-members, and thus is unable to teleport at all.
In general: Members may only teleport to their own team-members and their 'children'.
Teams are not limited to only two levels as in the above example. Another example:
teams.yml #2:
RAINBOW: members: - Godness RED: members: - Lesser GREEN members: - Least BLUE: members: - Notatall
Default and Joinable -attributes
teams.yml #3:
SUPER: members: - Godness RED: default: true joinable: true members: - Friend - Fisher - Froyd BLUE: default: true joinable: false members: - Devil - Daniel
Default-attribute
It is possible to make the plugin automatically assign new players into teams (on the first login, on the third login... this is configurable). The default-attribute defines the teams where new players can be assigned into. If a default-attribute is not present, the respective team will be unavailable for auto assignment (so no default-attribute and default: false is the same, really). All players will be assigned evenly between default teams (a default team being a team with default: true).
Say a new player joins the server and would be assigned to a team right away. In the above configuration he/she would be assigned into BLUE, since it's the team with the least members. If BLUE also had 3 members, the new player would be assigned into RED, since it's the first team the plugin finds.
Comments