-
Notifications
You must be signed in to change notification settings - Fork 255
How to assign players into groups
- About
- Option 1: Primary group from permission plugin
- Option 2: Permission nodes
- Taking groups from backend servers when TAB is on proxy
TAB uses groups to assign properties (such as tabprefix) and sort players in tablist (if sorting by groups). You have 2 ways of configuring primary groups of players in TAB.
First option hooks into your permission plugin and takes groups from it. Therefore, your permission plugin must be supported.
Supported permission plugins: LuckPerms everywhere, on Bukkit any plugin supporting Vault.
If your permission plugin is not supported, you can use Option 2.
This is the default method and recommended. TAB will ask your permission plugin for player's primary group. There are 2 simple steps to this:
- Keep
assign-groups-by-permissions: false
in your config - Put players into groups in your permission plugin
Caution
If assigning players into multiple groups, make sure their weights are correct (for luckperms /lp group <group> setweight <number>).
Tip
Verify player's group using /tab debug <player>
. It should say Primary permission group: <your group>
.
Instead of taking whole groups, TAB will check for permission nodes and assign groups based on the highest permission.
- Go to config.yml and set
assign-groups-by-permissions: true
. - Give
tab.group.<group name>
permission to the user/permission group. - Put all possible groups into
primary-group-finding-list
. This is necessary because:
#1 - there's no way to get the list of permissions, only checking for a permission. The list will be used for a list of permissions to check for.
#2 - if a player has permission for more than one group, the list will be used to pick the correct one (the one higher in the list).
Warning
Remember that OP = all permissions! That's the whole point of OP function. To grant all permissions. In that case, you need to negate permissions in your permission plugin for other groups which are higher than player's wanted group.
By default, TAB takes groups from the permission plugin installed on the same server instance.
In the case of proxy installation, groups are by default taken from the proxy.
To see how is your proxy permission plugin configured, use its respective command
(for LuckPerms it's /lpb user <player> info
instead of /lp
).
If you don't have your permission plugin synced using MySQL for sharing groups and don't wish to, and want groups to be taken from backend servers instead, enable the config option:
use-bukkit-permissions-manager: true
When enabling it, all group and permission requests will be done through Bridge plugin to take data from backend servers. Your groups will now match data from backend server a player is connected to (in case of LuckPerms /lp user <player> info
).
When assigning by permissions instead of taking the primary group directly from permission plugin,
the permission nodes (tab.group.<name>
) will be taken from backend servers instead.
- Why TAB?
- Installation
- Commands & Permissions
- Frequently Asked Questions
- Compatibility
- How to assign players into groups
- Known issues
- TAB-Bridge plugin
- Belowname
- Bossbar
- Global playerlist
- Header/Footer
- Layout
- Multi server support
- Nametags
- Per world playerlist
- Ping spoof
- Playerlist objective
- Scoreboard
- Sorting in tablist
- Spectator fix
- Tablist name formatting