Permissions
Player nodes are granted by default; you only touch them to take a command away from a group. Admin nodes are not granted by default.
Permission nodes
Section titled “Permission nodes”| Permission | Default | What it gates |
|---|---|---|
ks.achievements.user.use | ✅ allowed | /ksachievements and the Achievement Book item |
ks.achievements.user.titles | ✅ allowed | /kstitles |
ks.achievements.user.rewards | ✅ allowed | /ksrewards |
ks.achievements.admin | ❌ staff only | Every /ksachievementadmin subcommand, the admin window from every entry (command, /ksadmin hub, the showcase_achievements NPC) and every save or player action inside it |
ks.core.admin.dialog.console | ❌ staff only | Additionally needed to add, change or remove command rewards that run as the console (see below) |
The console has every permission.
Command rewards that run as the console
Section titled “Command rewards that run as the console”A command reward with "executor": "console" (also the default when the field is missing) runs with full server rights. To add, change or remove such a reward an admin needs both ks.achievements.admin and ks.core.admin.dialog.console. This is the same node KyuubiSoft Core uses for console commands in NPCs, dialogs and shops.
- Without the console node, these rewards are shown locked in the editor; everything else of the achievement stays editable.
- The server checks it again when saving and when a web editor import is applied.
- New command rewards created in the window run as the player.
- Existing console rewards keep working.
Other permissions
Section titled “Other permissions”| Permission | Notes |
|---|---|
ks.lootbag.admin | The “Lootbags” link in the admin window opens the admin of the KyuubiSoft Lootbags mod, which checks its own node |
ks.admin | Opens the KyuubiSoft hub (/ksadmin). The Achievements tile still needs ks.achievements.admin |
Showcase servers
Section titled “Showcase servers”While KyuubiSoft Core runs in showcase mode, every visitor may open the admin window read-only. Saving, player actions and the admin commands stay limited to real admins. The Players tab shows “Player data is hidden” to visitors, also when they hold ks.achievements.admin.
LuckPerms examples
Section titled “LuckPerms examples”# admin access for the staff group/lp group staff permission set ks.achievements.admin true
# allow trusted admins to edit console command rewards/lp group owner permission set ks.core.admin.dialog.console true
# take the book away from a restricted group/lp group spectator permission set ks.achievements.user.use falseMigration from older versions
Section titled “Migration from older versions”- The old node
achievements.adminhas no effect. Grantks.achievements.admin. ks.achievements.user.lootbagsno longer exists (the/kslootbagscommand was removed in 3.0.0).