Permissions

The mod declares twenty permission nodes. Eighteen are attached to commands - see Commands for which command needs which. The other two, cultivation.profile.test and cultivation.land.bypass, are checked at runtime, inside the sandbox profile and the land rules, and are not attached to any command. Not every command uses one of the twenty, either: a handful of read-only subcommands name no node of their own and are given one by the engine - see Generated nodes.

Hierarchy

The node names are dotted, and that dotting mirrors the command tree - cultivation is the root; cultivation.sect, cultivation.ascend, cultivation.celestial, cultivation.bounty, cultivation.array, cultivation.tide, cultivation.land, cultivation.market, cultivation.heaven, cultivation.sea, cultivation.calamity, cultivation.reincarnate, cultivation.quest, cultivation.admin, cultivation.profile.test and cultivation.debug sit under it; cultivation.land.bypass sits under cultivation.land; and cultivation.debug.vein and cultivation.debug.hotkeys sit under the debug group. Each command requires its own node explicitly, so holding cultivation does not by itself confer cultivation.admin.

The dotting is more than naming in one place. /cultivation debug vein and /cultivation debug hotkeys set no permission groups of their own, so the engine also asks for their parent's node: to use either, a player needs cultivation.debug as well as the leaf node. A wildcard on a staff group covers both.

What is granted by default

Fourteen nodes - cultivation, cultivation.sect, cultivation.ascend, cultivation.celestial, cultivation.bounty, cultivation.array, cultivation.tide, cultivation.land, cultivation.market, cultivation.heaven, cultivation.sea, cultivation.calamity, cultivation.reincarnate and cultivation.quest - are registered to the hytale:None group - the default group every player belongs to - so the whole player-facing experience, cultivating, sects, the Ascension capstone, reading the sky, the Bounty Board, the Transmission Array, the Beast Tide board, land protection, the Auction House, the Heavenly Realm, the Sea of Consciousness, the Calamity Beast, Reincarnation and quests alike, works out of the box with no permission setup.

Six nodes are granted to nobody by default - cultivation.admin, cultivation.debug, cultivation.debug.vein, cultivation.debug.hotkeys, cultivation.profile.test and cultivation.land.bypass - but not for the same reason:

• cultivation.admin and cultivation.debug are deliberately registered with an empty permission-group list rather than left unset. An unset list falls back to the parent command's groups, which would silently hand the admin menu to every player through hytale:None. Every staff-only subcommand that sits under another root - /celestial start, /tide trigger, /calamity trigger, /cultivation realms open and the rest - does the same. cultivation.debug.vein and cultivation.debug.hotkeys set no list of their own, so they inherit the debug group's empty one.
• cultivation.profile.test and cultivation.land.bypass are runtime-only checks. No command registers them to any group; the mod simply asks whether the player holds them at the moment of use, so they exist only where an operator has granted them.

Server staff still reach all of them the normal way, through the wildcard on their own admin group.

cultivation.profile.test is worth granting more deliberately than the others: it is not a debug convenience but a player-usable sandbox - anyone holding it can spin up a temporary cultivator with any realm, stage and Qi typed in by hand. A test cultivator is kept out of the rankings, sect scores and sect rosters, so the node is safe to hand to trusted balance-testers - but nothing about it is meant for hytale:None.

Generated nodes

A command that names no node of its own is given one by the engine: its parent's node, a dot, and its own name. Five read-only subcommands in this mod rely on that. Each is registered to hytale:None along with everything else, so nothing needs setting up.

They are not counted among the twenty because the mod never names them. Each stands on its own node, so denying the parent root does not by itself close one - deny the generated node as well if you want it shut.

What cultivation.admin covers

• The /cultivation admin config editor UI, and every subcommand under it: bypass, setrealm, setstage, setlevel, setqi, setlifespan, extendlifespan, reset, setrace, grantracechoice, grantskillpoints, granttechnique, revoketechnique, setlifebound, halloffame clear, npcdebug, the test sandbox tree, balance, heaven status (the old Heavenly Realm rebuild tool was removed in v0.11.0), inspect, backups and restore.
• Admin Inspect and Restore, the balance ledger and the admin bypass.
• The staff tools that sit beside the feature they control: /cultivation store status and recheck (on the root, not under admin), /cultivation merit grant, /cultivation rogue spawn and clear, /cultivation duel opentournament, /cultivation realms open and close, /celestial start, stop and rearm, /tide trigger and stop, and /calamity trigger and stop.
• Two checks made at runtime rather than on a command: re-anchoring a Secret Realm site with /cultivation array anchor (everyone else with cultivation.array can only re-anchor their own abode or a hall they lead or hold as elder), and the admin-only controls in the menus, such as the Admin tab and the celestial calendar's start and stop controls.

Admin Inspect and Restore

v0.10.3 Three cultivation.admin tools exist specifically to make an admin's own progress-changing commands safer to use, not to do more themselves:

• /cultivation admin inspect [player <player>] is a read-only look at a cultivator's full progress - it reads an online player live, and an offline one straight from their save file, and never changes anything. The same view is also reachable from an "Inspect & Restore" tab in the /cultivation admin menu.
• Every admin change to someone's progress - from a command or from the menu - now takes an automatic backup first, with no separate switch to turn that off.
• /cultivation admin backups [player <player>] lists those backups, newest first. /cultivation admin restore {id} previews and arms a restore of one by its id; nothing is applied until you follow it with /cultivation admin restore confirm, which reverses exactly what that one recorded change did. A restore only ever applies to an online player.

See Commands for the exact syntax of each.

The balance ledger

v0.10.3 /cultivation admin balance prints a local, aggregate-only usage summary for the mod's more recently shipped systems - Tea Ceremony, Transmission Arrays, Talismans, the Trial Pagoda, and Nascent Soul Escape - every one of which shipped with untested default numbers. It records counts only, never a player UUID or name, and nothing it records is ever sent anywhere. /cultivation admin balance reset clears every counter and restamps the since-time.