Permissions

Core Permissions

KyuubiSoft Core ships the cross-mod admin panel, config editor, citizen/NPC system, dev-export tools and the language manager. All admin functionality sits under ks.admin.*; citizens have their own ks.citizen.* nodes (see Citizens Permissions).

Admin Permissions

Permission	Default	Description
`ks.admin`	❌ staff only	`/ksadmin` — open admin panel + any subcommand without a more specific node
`ks.admin.reload`	❌ staff only	`/ksadmin reload` — reload all mod configs
`ks.admin.cleanup`	❌ staff only	`/ksadmin cleanup ...` — nameplate/NPC cleanup utilities
`ks.admin.migrate`	❌ staff only	`/ksadmin migrate-storage ...` — JSON ⇄ MySQL migration
`ks.admin.xp`	❌ staff only	`/ksadmin addxp`, `removexp` — LevelingCore XP grants
`ks.admin.editor`	❌ staff only	`/kseditor`, `/ksapplyconfig`, `/kstrusteditor` — Web Config Editor
`ks.admin.dev`	❌ staff only	`/ksdev` — developer data export (items, blocks, entities, citizens, worlds, emotes)

ks.admin acts as the umbrella: if a subcommand doesn’t have a more specific node (e.g. panel open), it requires ks.admin. Targeted subcommands have their own node — grant them individually to split roles across staff tiers.

Core Command Matrix

`/ksadmin`

Subcommand	Permission
(panel)	`ks.admin`
`reload`	`ks.admin.reload`
`cleanup nametags`	`ks.admin.cleanup`
`cleanup <other>`	`ks.admin.cleanup`
`migrate-storage file-to-mysql`	`ks.admin.migrate`
`migrate-storage mysql-to-file`	`ks.admin.migrate`
`addxp <player> <amount>`	`ks.admin.xp`
`removexp <player> <amount>`	`ks.admin.xp`

`/kseditor` family

Command	Permission
`/kseditor`	`ks.admin.editor`
`/ksapplyconfig <code>`	`ks.admin.editor`
`/kstrusteditor <nonce>`	`ks.admin.editor`

`/ksdev`

Subcommand	Permission
`items`, `blocks`, `entities`, `citizens`, `worlds`, `emotes`, `all`	`ks.admin.dev`

Alias for /ksdev: /dev.

Language — `/kslang`

Open to all players by design. No permission check; the Core plugin exposes per-player language selection and per-mod overrides via LanguageSettingsPage.

Core Shop Interaction — `ks.shop.user.use`

The Core citizen-shop interaction (citizen_shop) gates on ks.shop.user.use. This is separate from the player-shop system (ks.shop.*, see Shop System Permissions) — the Core shop runs server-owned merchant NPCs.

Citizens

Citizens use their own nodes. See Citizens Permissions:

ks.citizen — parent node for /kscitizen
ks.citizen.admin — all admin subcommands
citizen.interact.<custom> — per-NPC interaction gate (user-authored, config-driven)

LuckPerms Examples

# Full admin stack
/lp group owner permission set ks.admin true
/lp group owner permission set ks.admin.reload true
/lp group owner permission set ks.admin.cleanup true
/lp group owner permission set ks.admin.migrate true
/lp group owner permission set ks.admin.xp true
/lp group owner permission set ks.admin.editor true
/lp group owner permission set ks.admin.dev true
/lp group owner permission set ks.citizen.admin true

# Junior staff: reload + cleanup only
/lp group staff-jr permission set ks.admin true
/lp group staff-jr permission set ks.admin.reload true
/lp group staff-jr permission set ks.admin.cleanup true

# Web editor access for trusted builders
/lp group builder permission set ks.admin.editor true

Migration from Legacy Nodes

Legacy	New
`kyuubisoft.admin`	`ks.admin`
`citizen.admin`	`ks.citizen.admin`
`kyuubisoft.editor`	`ks.admin.editor`
`dev.admin`	`ks.admin.dev`

The legacy nodes are no longer checked — update LuckPerms grants to the new nodes.