Permissions
Nameplates Permissions
Section titled “Nameplates Permissions”The Nameplates mod uses ks.nameplate.* plus per-tag permission strings.
Permission Nodes
Section titled “Permission Nodes”| Permission | Default | Description |
|---|---|---|
ks.nameplate.user.use | ✅ allowed | Player nameplate toggle commands (select, clear, list) |
ks.nameplate.admin | ❌ staff only | Admin subcommand — reload, config, force-grant, debug |
Player Commands
Section titled “Player Commands”| Command | Permission | Description |
|---|---|---|
/ksnameplate list | ks.nameplate.user.use | List available tags you can equip |
/ksnameplate select <tag> | ks.nameplate.user.use + per-tag permission | Select an active tag |
/ksnameplate clear | ks.nameplate.user.use | Clear your active tag |
Each individual tag additionally checks a per-tag permission string configured in the tag’s entry (via TagManager.hasPermission). The per-tag string can be anything — the mod just calls hasPermission() on whatever you set.
Admin Commands
Section titled “Admin Commands”| Command | Permission | Description |
|---|---|---|
/ksnameplate admin ... | ks.nameplate.admin | Reload, force-grant, debug |
The admin subcommand additionally checks a custom permission from config.adminPermission (defaults to ks.nameplate.admin). Rename in config if you want a different node.
Per-Tag Dynamic Permissions
Section titled “Per-Tag Dynamic Permissions”Each tag definition may include a permission string:
{ "id": "vip_crown", "name": "Crown", "permission": "nameplate.tag.vip", ...}Only players with nameplate.tag.vip (or whatever string you choose) can equip the tag. Omit the permission to make a tag available to everyone.
LuckPerms Examples
Section titled “LuckPerms Examples”# Staff admin/lp user Steve permission set ks.nameplate.admin true
# VIP tag access/lp group vip permission set nameplate.tag.vip true