Permission Nodes
In: Reference · Related: Command Reference · Back: Home
QR has only two permission nodes — an extremely lean structure: one base permission for all players and one umbrella permission for admins. Verified against plugin.yml.
Permission node table
| Node | Default | Description |
|---|---|---|
qinhruins.use | true (everyone) | Use QR's base commands (list / near / activate / codex / reroll / reward / party / guide cancel) |
qinhruins.admin | op (admins only) | All of QR's admin permissions. Automatically includes qinhruins.use (children: qinhruins.use: true) |
The
childrenconfig onqinhruins.adminmeans: granting admin automatically grants use — no need to grant use separately.
Permissions required per command
No permission required
| Command | Note |
|---|---|
/qr, /qr help | The help menu; the source attaches no permission, so anyone can view it |
qinhruins.use (players)
version, list, near, activate, codex, reroll, reward, party create, party invite, party accept, party leave, party info, guide cancel.
qinhruins.admin (admins)
reload, pos1, pos2, save, spawn, gentest, why, scatter, stage *, import, tp, remove, markers, guide clear, keystone give, genstruct, editor *, info, profile.
The subcommands of
stage *andeditor *inherit, in the source, theqinhruins.admindeclared on their respective parent nodes (stage/editor), so the whole group requires admin permission.
For the full line-by-line mapping, see Command Reference.
Suggested permission group setup
Regular player group (default)
No configuration needed — qinhruins.use defaults to true, so all players get base exploration / realm / party / codex features out of the box.
If you want to tighten it (for example, disable self-service realm activation by regular players), explicitly revoke it with a permission plugin:
# LuckPerms example: revoke use from the default group
permissions:
- qinhruins.use: falseBuilder / operations group (builder)
If you want certain GMs to be able to build ruins, tune generation, and grant keystones, but you don't want to give the full OP set:
# Grant the admin umbrella permission directly (already includes use)
permissions:
- qinhruins.admin: trueQR has no finer-grained sub-permissions; qinhruins.admin is "all or nothing." If you need to split "grant keystones" and "reload" across different people, control it at the permission-plugin level with command allow/deny lists (such as LuckPerms' command context); QR itself does not split it.
Protection bypass
Ruin protection (Spawning & Clearing) automatically lets through holders of qinhruins.admin: admins can break placed blocks inside exploring / activating ruins, which is convenient for on-site debugging. Granting the builder group admin also grants the bypass capability.