Permissions
Every permission node EssentialsC registers, what it controls, and who gets it by default.
Overview
Every feature in EssentialsC is gated behind a permission node under the essentialsc. namespace - usually essentialsc.<feature>, with finer sub-permissions like essentialsc.sethome.admin for admin-only behavior within that feature.
EssentialsC doesn't manage permissions itself. It registers nodes through Bukkit's standard permission system, so any Vault-compatible permissions plugin works - most servers use LuckPerms.
Default Levels
Every node ships with one of three defaults, which decides who has it without any permissions plugin involved at all:
| Default | Who has it out of the box |
|---|---|
| Everyone | Granted to every player automatically - no setup needed. Used for everyday commands like /balance or /tpa. |
| Operators | Granted automatically to server operators only. Non-op players need it explicitly granted through a permissions plugin. Used for admin and moderation features. |
| Nobody | Nobody has it by default, op or not - it must always be granted explicitly. Used for tiered features, like the per-amount essentialsc.sethome.5 style home limits. |
Wildcards
A handful of nodes are wildcards that bundle related sub-permissions together, so granting one node covers all of them - for example essentialsc.kits.* covers every kit-related permission, including admin management.
Most permissions plugins also support wildcarding the entire plugin. With LuckPerms, granting essentialsc.* to a group gives that group every node on this page in one line:
/lp group admin permission set essentialsc.* true