Permissions
Node reference
| Node | Default | Grants |
|---|---|---|
aquacore.help | true | /aqua help |
aquacore.reload | op | /aqua reload |
aquacore.modules | op | /aqua modules |
aquacore.args | op | /aqua args |
aquacore.broadcast | op | /aqua broadcast |
aquacore.preview | op | /aqua preview |
aquacore.debug | op | /aqua debug dump |
aquacore.notify.update | op | Update message on join |
aquacore.bypass.cooldown | false | Ignore broadcast cooldowns |
aquacore.admin | op | Everything above |
default is what a player has when no permission plugin is installed. op means only
operators hold it, true means everyone does, false means nobody does until it is granted.
Recommended setup
LuckPerms
/lp group staff permission set aquacore.broadcast true
/lp group staff permission set aquacore.preview true
/lp group admin permission set aquacore.admin true
/lp group default permission set aquacore.help trueConsole-only actions
Some actions are deliberately unreachable from in-game, no matter which node a player holds:
/aqua broadcastwhenbroadcast.console-only: true(the default)./aqua debug dumpwhen the dump would include the server IP.
A player attempting either gets:
This command can only be executed from console.Do not grant * to your staff group. It hands out every node registered by every plugin on the
server, including ones marked console-only by other authors. Grant aquacore.admin instead.
Per-template permissions
Templates can require their own node. Add permission to the template file:
templates/vip.yml
permission: aquacore.template.vipThen the broadcast only fires for senders holding that node. Useful when different staff ranks are allowed to announce different things.
Last updated on