Permissions
The mod declares eleven permission nodes. Every command in the mod sits behind one of them - see Commands for which command needs which.
| Permission | Description |
|---|---|
cultivation | The /cultivation root and every player-facing subcommand under it - info, bind, meditate, hud, settings, race, skilltree, dao, technique, refine, respec, bonuses, formations, abode, beast, duel, top, profile, aura, alchemy, masterdisciple, deviation, realms, talisman, oath, spirit, market. |
cultivation.sect | The /sect root and every sect subcommand, including /sect war, /sect banner, /sect top and the 0.8.0 economy suite - donate, pavilion, mission, tournament, abbr. The same suite reached through /cultivation sect ... uses this node too. |
cultivation.ascend v0.8.0 | /ascend and its begin and prestige branches - the Ascension capstone. |
cultivation.celestial v0.8.0 | /celestial and /celestial list - reading what celestial event is overhead. Starting and stopping one is cultivation.admin instead. |
cultivation.bounty v0.9.0 | /bounty and its list and contracts branches - the Bounty Board. A standalone root command rather than a /cultivation subcommand, so it needs this node instead of the base cultivation one. |
cultivation.admin | The /cultivation admin config editor UI, its player-modifying subcommands, the /cultivation admin test tree, the admin bypass, the store-sync tools, /cultivation realms open/close, and /celestial start/stop. |
cultivation.profile.test v0.7.0 | The test-profile sandbox on your own account: /cultivation profile test and its realm/stage/qi/points/race/reset branches. Since v0.7.3 the sandbox is command-only — it no longer appears in the Profiles menu, and granting one to another player is cultivation.admin instead. |
cultivation.land.bypass | Ignores every land claim's rules, everywhere — sect halls, sect ground and cave abodes alike. |
cultivation.debug | The /cultivation debug command group. |
cultivation.debug.vein | /cultivation debug vein. |
cultivation.debug.hotkeys | /cultivation debug hotkeys. |
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.admin, cultivation.profile.test and cultivation.debug sit under it; 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.
What is granted by default
cultivation, cultivation.sect, cultivation.ascend, cultivation.celestial and cultivation.bounty are all 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 and the Bounty Board alike, works out of the box with no permission setup.
cultivation.admin, cultivation.profile.test, cultivation.debug, cultivation.debug.vein and cultivation.debug.hotkeys are granted to nobody by default. They 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. Server staff still reach 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.