Palettes
Eight complete looks, each a full recolor of Cultivation's menus, HUD and skill tree.
The eight
Jade Slip groups its palettes into the same two captioned sections the picker shows them under:
Sect Halls — Frost Peak · Verdant Hall · Starfall Peak · Jade Dawn
Paths — Bloodmoon · Golden Court · Ink Wash · Lantern Court
The first five — Frost Peak, Verdant Hall, Bloodmoon, Golden Court and Ink Wash — are the original set. Starfall Peak, Jade Dawn and Lantern Court followed later, and each has its own Codex lore entry describing what wearing it is said to say about a cultivator.
What "themes every menu" covers
Each palette is a complete set of 106 recolored .ui documents — every page, every card, the HUD, the admin menu, and the skill tree's nine branch halos, which are the fiddliest part of a palette and the one most likely to be skipped. Nothing is half-themed: a palette that recolored four of the nine halos and left five in Cultivation's own crimson would read as a bug rather than a look, so Jade Slip's palettes set all nine or none.
That document count has grown release over release — 61 at launch, 77 once Cultivation's v0.8.0 and v0.9.0 pages were folded in, 106 as of the current build. Each palette is regenerated from Cultivation's own source tree, so a page the base mod adds gets a themed variant the next time Jade Slip is regenerated against it — not automatically the moment Cultivation ships.
Add-on pages get themed too
The document set isn't limited to pages Cultivation itself ships. It also covers pages belonging to other add-ons the palette generator has been run against — currently Soul Rings and the Classes add-on. A server running either alongside Jade Slip gets those pages drawn in your chosen palette rather than left in the base look while everything around them changes color.
An add-on the generator hasn't been pointed at yet simply keeps its own default look under any palette — resolving to a document that doesn't exist would fail the entire UI load on the client, not just the untracked page, so Jade Slip only ever redirects a document it has an explicit, generated variant for.
Choosing one
Palettes are selected from the theme dropdown in Cultivation's Settings page, the same list every installed look from any mod appears on. Jade Slip shipped its own separate Palettes page through v0.1.1; it was removed in v0.1.2 once that shared dropdown existed, because a second tab for one mod's looks was always the lesser answer once a single list could hold everyone's.
Your saved choice carries over untouched between Jade Slip versions, and you can change it whenever you like. If Jade Slip is later removed from a server, a palette you had chosen keeps its id stored — Cultivation saves the id, never the palette itself — and resolves to its own default the moment nothing claims that id; the choice returns intact if Jade Slip comes back.
Gating a palette behind a permission
By default every palette is everyone's — installing Jade Slip is the whole purchase, and no look is held back. An owner who would rather hand palettes out individually, as a rank reward rather than a blanket unlock, turns on Palettes-Require-Permission in the config or Cultivation's admin menu. Once it's on, each palette needs its own jadeslip.palette.<id> node — jadeslip.palette.frost, jadeslip.palette.starfall, and so on for all eight.
The gate gates choosing, not keeping. A player who picked a look before the toggle went on keeps wearing it, and the check is only asked again the next time a menu is opened or a new palette is picked — so turning the toggle on before handing looks out is what makes it bind from the start. See For Server Owners for the full config reference and exactly which settings take effect immediately versus on the next restart.