Vault & LuckPerms
BusyTab reads ranks, prefixes and suffixes from Vault (or VaultUnlocked) and from LuckPerms. You can use either one, or both.
Vault / VaultUnlocked
Detected at startup when a plugin named Vault is enabled and a permission plugin has registered
with it. BusyTab logs Hooked into Vault/VaultUnlocked.
| Placeholder | Comes from |
|---|---|
%vault_rank% |
The primary group from Vault's permission provider |
%vault_prefix% |
The player's prefix from Vault's chat provider |
%vault_suffix% |
The player's suffix from Vault's chat provider |
Vault on its own supplies nothing. It passes on what your permission plugin (LuckPerms, for example) registers. If only one of the two providers is registered, the placeholders for the other show nothing.
LuckPerms
Detected at startup when LuckPerms is enabled. BusyTab logs Hooked into LuckPerms. and reads
straight from the LuckPerms API. The LuckPerms PlaceholderAPI expansion is not needed for these:
| Placeholder | Comes from |
|---|---|
%luckperms_primary_group_name% |
The player's primary group |
%luckperms_prefix% |
The player's current prefix |
%luckperms_suffix% |
The player's current suffix |
Which should I use?
- Just LuckPerms: use the
%luckperms_...%placeholders and change the default%vault_rank%intablist-name-format,footerandnametag.prefixto%luckperms_primary_group_name%or%luckperms_prefix%. - LuckPerms with Vault: the default config works as shipped.
- Another permission plugin: install Vault and use the
%vault_...%placeholders.
Sorting
The rank used for Rank Sorting comes from Vault first, then LuckPerms. You don't have to show the rank anywhere for sorting to work.
Prefixes with colors
A prefix can contain & codes, &#RRGGBB hex, MiniMessage tags or Nexo glyphs. BusyTab formats
them after inserting the prefix. For example, set a LuckPerms prefix with:
/lp group admin meta setprefix 100 "&c[Admin] "