Permissions
##Introduction
Permissions control who can access each feature of Aevum. 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 |
|---|---|---|
| aevum.admin | aevum.timer, aevum.stopwatch, aevum.reload |
Full access to every Aevum feature. Reserve for administrators. |
| aevum.timer | — | Access to all timer commands (/aevum timer …). |
| aevum.stopwatch | — | Access to all stopwatch commands (/aevum stopwatch …). |
| aevum.reload | — | Use /aevum reload. |
##Explanation
- Tree structure — Granting
aevum.adminunlocks the entire plugin, because it includesaevum.timer,aevum.stopwatchandaevum.reload. Grant the children individually for finer control. - Per-feature access —
aevum.timerandaevum.stopwatchare independent, so you can let someone manage stopwatches without touching timers, or vice versa. - Reload —
aevum.reloadis split out so trusted staff can reload the config without full admin 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.
INFO
The /aevum help menu is available to anyone who can run a command they have access to. Players without any Aevum permission simply can't use the command.