Roles & Permissions
The four team roles, what each one can do, how promote, demote, kick and transfer work, and how to change it.
Every member of a team has one of four roles. Roles decide what a member can do inside their team;
they are not server permission nodes and are configured under Roles in
config.yml.
The ladder
Section titled “The ladder”From highest to lowest:
- Leader - exactly one per team, holds every permission
- Co-Leader
- Moderator
- Member - every new member starts here
Role permissions
Section titled “Role permissions”Each role except the Leader lists what it is allowed to do:
| Permission | Allows | Default roles |
|---|---|---|
Invite |
/team invite, the Invite Player button |
Co-Leader, Moderator |
Kick |
/team kick, shift click in the members menu |
Co-Leader, Moderator |
Promote |
/team promote, left click in the members menu |
Co-Leader |
Demote |
/team demote, right click in the members menu |
Co-Leader |
Home |
/team home, the Team Home button |
Co-Leader, Moderator, Member |
Set-Home |
/team sethome, /team delhome, the Set Team Home button |
Co-Leader |
Rename |
/team rename, the Rename Team button |
Co-Leader |
Friendly-Fire |
the Friendly Fire toggle | Co-Leader |
Open |
the Open Joining toggle | Co-Leader |
The Leader always has all of them. Some things are not permissions at all:
- Leader only: disband and transfer.
- Every member: team chat,
/team info, opening the members and settings menus (the buttons in them still check the role), and leaving (everyone except the Leader).
Roles: Leader: Display-Name: "&6Leader" Co-Leader: Display-Name: "&eCo-Leader" Permissions: - "Invite" - "Kick" - "Promote" - "Demote" - "Home" - "Set-Home" - "Rename" - "Friendly-Fire" - "Open" Moderator: Display-Name: "&aModerator" Permissions: - "Invite" - "Kick" - "Home" Member: Display-Name: "&7Member" Permissions: - "Home"Permission names are case-insensitive, and Set_Home works as well as Set-Home. An unknown name
fails the load. Roles.Leader must not have a Permissions list; adding one fails the load.
Ranking rules
Section titled “Ranking rules”On top of the role permission, managing another member follows these rules:
- Kick, promote and demote only reach members ranked below you. A Co-Leader cannot touch another Co-Leader.
- A promotion must stay below your own role. A Co-Leader can promote a Member to Moderator, but only the Leader can make someone a Co-Leader.
- Nobody is promoted to Leader. Promoting a Co-Leader is refused with
CANNOT-PROMOTE; use/team transfer <player>instead. - Demoting a Member is refused with
CANNOT-DEMOTE; they already have the lowest role. - You can never target yourself.
Members menu
Section titled “Members menu”/team members (or the Team Members button) lists every member, highest role first, then by name.
| Click | Does |
|---|---|
| Left click | Promote one role |
| Right click | Demote one role |
| Shift click | Open the kick confirmation |
A refused click flashes the Not-Allowed icon and plays the DENIED sound, and the chat message says
why. The leader uses Leader-Icon, everyone else Member-Icon; both are set in
members-menu.yml.
Transferring leadership
Section titled “Transferring leadership”/team transfer <player> opens the confirm menu. On confirm, the target becomes Leader and the old
leader becomes Co-Leader. Only the Leader can transfer, and the target must be in the team.
Display names
Section titled “Display names”Display-Name is what {role} shows in messages, team chat, member icons, /team info and
%optimalteams_role%. The roster lines in the team top menu use their own names from
Roster-Roles in top-menu.yml, so you can keep those short.
After editing, run /teamadmin reload.
