SulfurLabPermissions
##Introduction
Permissions control who can access each feature of SulfurLab. The nodes are organized as a tree: the parent node automatically grants its children, so you can give broad access with a single permission or fine-tune it. Every node defaults to op.
##Permission Tree
| Permission | Grants (children) | Description |
|---|---|---|
| sulfurlab.admin | sulfurlab.sulfur, sulfurlab.reload |
Full access to every SulfurLab feature. Reserve for administrators. |
| sulfurlab.sulfur | — | Manage Sulfur Cubes — every cube command (new, list, info, set, unset, block, rename, tp, tphere, glow, kill). |
| sulfurlab.reload | — | Use /sulfurlab reload. |
##Explanation
- Tree structure — Granting
sulfurlab.adminunlocks the entire plugin, because it includes bothsulfurlab.sulfur(all cube management) andsulfurlab.reload. Grant the children individually if you want finer control. - Cube management —
sulfurlab.sulfuris the one node that covers the whole/sulfurlabcube toolkit. A player either can manage cubes or can't; there are no per-subcommand nodes. - Reload —
sulfurlab.reloadis split out so you can let trusted staff reload the config without giving them cube-editing powers. - Defaults — Every node defaults to
op, so a fresh install gives operators full control and regular players nothing until you assign nodes via a permissions plugin like LuckPerms.