-
Notifications
You must be signed in to change notification settings - Fork 1
Permissions
j-gaertig-co-dev edited this page Aug 13, 2026
·
2 revisions
Every PlainBase permission defaults to OP. Regular (non-OP) players have access to no PlainBase command out of the box — you have to grant permissions explicitly through your permissions plugin (LuckPerms, PermissionsEx, ...).
/lp group default permission set plainbase.teleport.tpa.tpa true
Permissions follow a consistent hierarchy:
plainbase.<module>[.<subfeature>].<command>
Admin nodes exist at every level and grant everything below them:
| Node | Grants |
|---|---|
plainbase.admin |
Everything — every command in every module, plus /plainbase reload|toggle|update. |
plainbase.<module>.admin |
Every command of that one module (e.g. plainbase.vanish.admin). |
plainbase.teleport.tpa.admin |
Every TPA command (Teleport module has two independent admin nodes: tpa and rtp). |
plainbase.teleport.rtp.admin |
Every RTP command. |
Use the highest admin node that fits your rank structure instead of granting dozens of individual command permissions.
| Module | See |
|---|---|
| Spawn | Module-Spawn |
| Teleport (TPA & RTP) | Module-Teleport |
| Join Items | (config-only, no permissions) |
| Messages & Broadcasts | (config-only, no permissions) |
| Vanish | Module-Vanish |
| Menu | Module-Menu |
| Moderation | Module-Moderation |
| Team | Module-Team |
| Command | Permission |
|---|---|
/plainbase reload |
plainbase.admin |
/plainbase update |
plainbase.admin |
/plainbase toggle <module> |
plainbase.admin |
There is intentionally no separate, lower-tier permission for /plainbase sub-commands — they're all considered server-admin-only.