Repository navigation
v0.38.2 - independent mounts with their own turn, full rules for every agent program, lobby corners for Arcane, Hearth and High Kingdoms, Power Surge after a spell attack, and Next.js 16.4.6
LatestA creature you ride can be its own mount with its own turn, the storyteller keeps the full rules on every agent program, Arcane, Hearth and High Kingdoms get lobby corners you can see, a wizard's spell attack opens Power Surge again, and Next.js 16.4.6 with a fix for big WorldForge worlds.
Mounts
- An independent mount keeps its own turn. A called-up creature sent with
controlled: falsekeeps its place in the initiative order, and the GM plays its turn. Its move carries its rider's token at the mount's own speed, with its own Dash. On the rider's turn the rider cannot move the pair; getting down and standing up in the saddle still cost half the rider's speed. A mount with no creature of its own, such as a listed elk or griffon or one written by hand, is ridden as a controlled mount, and the result says why. (#1044, by Smoebo, fixes #1036) - A forced move cannot outrun an independent mount. A forced move that names the mount on its own turn now counts as the mount walking, so it stops at the mount's speed.
- An area that names both a rider and the mount hits the mount once. Before, the mount took the blast twice.
Storyteller
- The full rules are the only supported setup. The storyteller needs a 64K context window to play the full rules, and every guide,
npm run setupand the window-too-small message now give that one figure. Story model pickers leave off models that cannot hold the full rules, though you can still type one in by hand. (#1052, fixes #1047) - Every agent program keeps the full tool set. The party lead's direction now comes after the current moment, as it does on the chat path. A blank bookkeeping effort uses the story's effort only when the bookkeeping model offers it.
- The Antigravity CLI is not supported. It cannot load the full tool set, so it plays the compact rules with only each call's tools, and it is left off the program lists. An admin who chooses it anyway with Add it anyway sees a warning. Its lockdown checks the 60 built-in tools it reports at startup and denies the risky ones by name. bkruggel tested a signed-in turn and a picture against it. Effort levels, quota and native pictures come from #1046 (by bkruggel).
Rules
- A wizard's spell attack through
pc_attackopens Power Surge again. The unified attack path had stopped marking the spell's damage. (#1053)
Themes
- Arcane, Hearth & Haven and High Kingdoms paint their own lobby corner pieces at the size Woodland, Tide and Forge show, mirrored into all four corners, with phone sizes that keep their proportion to the rail. Gothic keeps its frame corner until its new piece is repainted: mirrored into the lower corners, its spires hung upside down. (#1049, by Smoebo)
- The theme check gets past its shared artwork step again, and the theme guide explains what mirroring does to the two lower corners.
Under the hood
- Next.js 16.4.6, which clears seven moderate advisories in 16.4.1. (#1050)
- Big worlds open again on Next 16.4.6. That release drops a route's Content-Encoding header and gzips the answer itself, so a world over 64 KB came back gzipped twice and did not open. The WorldForge page now asks for the packed answer and unpacks it itself, and every other caller gets plain JSON.
- French menus on a cold load no longer throw React's "use() did not call use()" error. (#1051, by bkruggel)
- Dead code is gone and stays gone. 166 unused locals and parameters, 110 unused exports and one unused file are removed, and CI fails if new dead code appears. Every jsx-a11y rule is on, and every route parses its request body with zod. (#1053, refs #570)
Full changelog: v0.38.1...v0.38.2