Admin and Config
Everything a player can see is /sacredbody (alias /body) with no arguments — open to anyone, permission-wise, since it only reports what the caller already has. Everything that changes a constitution sits behind cultivation.admin, the same permission Cultivation's own admin tools use, so a server that already has admins configured needs no new grant.
Commands
/sacredbody reports what the caller was born with: their sacred body (if any) with its description, and every physique they hold with its tier and description. A cultivator who rolled nothing is told that plainly rather than shown an empty list.
| Command | What it does |
|---|---|
/sacredbody reroll | Re-rolls the caller from scratch — clears whatever body and physiques they had, then draws again on the same table a fresh login would use. |
/sacredbody reroll player <player> | The same, targeting another online player. |
A re-roll discards the previous result entirely; there is no way to recover what was rolled before it.
| Command | What it does |
|---|---|
/sacredbody set <body> | Grants the caller a specific sacred body by id, or strips it with /sacredbody set none. |
/sacredbody set player <body> <player> | The same, targeting another online player. |
Setting a body also marks the target as already-rolled, so it survives their next login rather than being overwritten by the automatic one-time roll. If the body named is currently disabled in config (see Availability below), the command still grants it but warns the admin that it presently does nothing.
| Command | What it does |
|---|---|
/sacredbody physique add <physique> | Grants a physique to the caller, tier drawn from the configured weighted table. |
/sacredbody physique add <physique> <tier> | The same, at a stated tier (legendary, king, saint, or immortal) instead of a random one. |
/sacredbody physique add player <physique> [tier] <player> | Either form, targeting another online player. |
Granting a physique the target already holds overwrites its tier rather than refusing — an admin naming a tier is stating what it should be. The command reports the tier that was replaced, so silently downgrading someone's Immortal-tier physique to Legendary by accident is something you'll see happen, not something that happens quietly.
| Command | What it does |
|---|---|
/sacredbody physique remove <physique> | Takes one physique back from the caller. |
/sacredbody physique remove player <physique> <player> | The same, targeting another online player. |
| Command | What it does |
|---|---|
/sacredbody physique clear | Takes every physique the caller holds back at once. |
/sacredbody physique clear player <player> | The same, targeting another online player. |
Every subcommand that changes something also re-applies the caller or target's flat stat bonuses (Windless Step's stamina, Undying Marrow's health) immediately, so a grant or removal takes effect without a relog.
The admin config page
Every number this add-on uses is registered as a section of Cultivation's own in-game admin config editor — no separate menu, no restart, and no file edit required for a value that already exists. Only the rolling section also appears on Cultivation's Settings page; the rest are admin-page-only, so tuning forty-odd balance numbers doesn't turn the Settings page into a second admin page.
Rolling
The one section shown to owners outside the full admin page too.
| Setting | Default | What it does |
|---|---|---|
| Sacred Bodies Enabled | true | Turns off the entire sacred-body half of the roll. Off, none roll and one already held grants nothing. |
| Physiques Enabled | true | The same, for the physique half. Sacred bodies are unaffected either way. |
| Sacred Body Chance % | 2.5 | The chance a cultivator's one roll gives them a body at all. |
| Physique Chance % | 3 | Rolled once per enabled physique, independently — this is what makes holding two rare rather than impossible. |
| Announce On Roll | true | Whether a cultivator is told in chat what they were born with, the moment they're rolled. |
Tiers
Tier-Weight-* and Tier-Multiplier-* for each of Legendary, King, Saint, and Immortal — see The Eight Physiques for what the defaults are and how the weighting works.
Shared
The bonuses every sacred body grants regardless of which one it is:
| Setting | Default |
|---|---|
| All Bodies Qi % | 5 |
| All Bodies Damage Reduction % | 3 |
| All Bodies Stamina % | 5 |
| All Bodies Aura Scale % | 20 |
| Base Stamina | 100 — what the stamina percentages (here and Windless Step's) are taken of. A flat figure rather than a live read of the player's current maximum, because the bonus is itself part of that maximum and reading it live would compound on every re-apply. |
Bodies
Every per-body number from The Sixteen Bodies — Ancient-Damage-Reduction-Percent, Ancient-Yin-Resistance-Percent, Ancient-Balance-Tolerance-Percent, DaoFetus-Qi-Percent, DaoFetus-Ritual-Ease-Percent, DaoFetus-Charge-Time-Reduction-Percent, Firmament-Damage-Percent, Firmament-Unarmed-Damage-Percent, Elemental-Qi-Percent, Elemental-Dao-Affinity-Percent, Yin-Body-Yin-Shift-Percent, Yin-Body-Fragility-Percent, Yang-Body-Yang-Shift-Percent, Yang-Body-Lava-Qi-Percent, and Yang-Body-Immune-Damage-Causes — a free-text, comma-separated list of DamageCause asset ids the Yang Body cannot be hurt by (default Fire, Cultivation_Fire, Lava, Burn). An id that doesn't resolve to a real DamageCause is simply never matched, rather than erroring.
Physiques
Every per-physique number from The Eight Physiques — Tyrant-Damage-Percent, Tyrant-Fragility-Percent, YinYangEyes-Balance-Tolerance-Percent, SpiritSea-Qi-Percent, HundredMeridians-Charge-Time-Reduction-Percent, JadeBone-Damage-Reduction-Percent, WindlessStep-Stamina-Percent, HeavensBlindSpot-Ritual-Ease-Percent, and UndyingMarrow-Health — each expressed before its tier multiplier is applied.
Availability: per-body and per-physique checkboxes
Disabled-Bodies and Disabled-Physiques are comma-separated id lists on disk, but the admin page never asks an owner to type an id by hand — it renders one checkbox per sacred body and per physique instead, built dynamically from the same open registry the roll itself reads. That has a real consequence: because it's built from the live registry rather than a fixed list, a body or physique contributed by a different add-on gets a checkbox here automatically, without this add-on needing to know that add-on exists.
Unchecking one removes it from the roll pool immediately and, per the source's own documentation, "grants nothing to a cultivator who already has it" — but the row itself is not deleted from anyone's save, and it is not silently forgotten: an admin who tries to grant a disabled body or physique with /sacredbody set or /sacredbody physique add is warned that it currently does nothing, rather than being refused outright. That's deliberate — flipping a body off today and back on next month should restore it for everyone who was already holding it, with nothing to re-grant.
Disabling a body or physique is per-thing, not per-category — a server owner who wants the ten elemental bodies without Chaos Divine unchecks exactly one box, not all sixteen.
What takes effect when
Every number above is read live, at the moment it matters — a modifier channel being asked, a roll being made — so nothing here needs a server restart. The one thing a config change cannot do is revisit a cultivator who has already had their one roll; that's what /sacredbody reroll is for, and it should be used with the same care described on Getting Started.
Compatibility
Sacred Bodies declares Siren:Cultivation: ">=0.7.4" as a hard dependency in its manifest — a server running an older Cultivation is refused at load, before a line of this add-on's code runs. On top of that, it checks in with xianxia.dev to confirm it's a genuine, current build and reads the published compatibility list. If a future Cultivation release turns out to break this build, the add-on stands its modifier source and admin pages down and says exactly why in the console, rather than quietly mispricing combat — but it never touches a saved constitution. Every cultivator keeps the body and physiques they were born with, and everything resumes on the next boot once the versions match. It fails open in every direction: an offline server, or one behind a strict firewall, is never affected by a failed check.