AscendPermissions
The two permission nodes AscendSMP uses, what each one grants, and who has them by default.
AscendSMP keeps permissions simple: there are exactly two nodes. One covers everything a normal player does, the other covers everything an admin does. Set them with any permissions plugin you already use.
The two nodes
| Permission | Default | Grants |
|---|---|---|
ascend.use | Everyone | Using abilities: the activation key, /spark, /sparkgui, and the HUD toggle (/ascend hud toggle). |
ascend.admin | Operators only | Every /ascend management subcommand: reroll, setsecondary, setprimary, event, info, level, give, and reload. |
Because of the defaults, a fresh install needs no permissions setup at all: regular players can play, and ops can administrate.
The base `/ascend` command only requires `ascend.use`, because it also carries the player-facing HUD toggle. The management subcommands then check `ascend.admin` on their own. So giving someone `ascend.use` does not let them touch any admin subcommand.
What each command needs
| Command | Needs |
|---|---|
/sparkgui (aliases /abilities, /amenu) | ascend.use |
/spark <primary\|secondary> (alias /ability) | ascend.use |
/ascend hud toggle | ascend.use |
All other /ascend subcommands | ascend.admin |
For the full per-command table with descriptions, see Commands.
Want ability use limited to certain players or worlds? You can deny `ascend.use` through your permissions plugin, and `config.yml` also has a `disabled-worlds` list; see [Configuration](/docs/configuration/).
Questions? Ask on Discord: discord.arrowtan.cc, or check the FAQ.