The belt becomes a real place, emotes replace speech bubbles, and CMS writes actually work now
Six phases of ship progression landed in Cultures of the Belt in a single day. Precursors creatures stopped talking in text and started expressing themselves in animations and sounds. And the CMS write endpoints that were silently returning 404 on every mutation? Fixed, redeployed, and playtested.
What shipped
Six phases of ship progression in one day
The ShipPowers registry now gates all player capabilities behind ship upgrades, with a dev-mode unlockAll() escape hatch for testing. Scanner tiers gate the creature info panel — basic scanners show vitals, advanced scanners reveal full biochemistry. Fog of war arrived: rooms start dark until a creature enters them.
Asteroid navigation became real: each asteroid has a velocity relative to the player's base, making delta-v the scarce resource. Low delta-v targets are cheap to reach; high delta-v ones demand commitment. Transit between asteroids now carries micrometeorite danger that scales with distance. And a power system (battery, solar trickle-charge, harvester charging stations) adds resource management to ship operations.
Combined with yesterday's Ceres and Vesta trade hubs, the belt now feels like a place with rules, costs, and consequences.
Emotes trigger animations now, not speech bubbles
v0.4.53 shipped with a fundamental change to creature expression. When the LLM produces emotes like gurgle or whimper, they now trigger visual animations and sound effects instead of appearing as text in speech bubbles. Creatures communicate through body language, not subtitles.
LimbicNN was retrained with proper DrivaKemm chemical weighting. The admin allowlist fix reached production. And the CMS entry went live on the library page — with a Cloudflare edge purge to make sure the cached version actually updated.
Norn behavior verified, design breakthrough crystallized
Three long-standing behavior verifications passed: Norns think at approximately 1/sec with no LLM request bursting, approach each other naturally for socializing without the old 200px flee distance, and crowding builds gradually as designed. LimbicNN was retrained. The analytics script 404 on the play site was fixed.
A design breakthrough crystallized: in MVEE, the player is "the Chorus" — part of a cross-game narrative thread where each title gives you a different relationship to the beings you watch over. This is the connective tissue between all Multiverse Studios games.
Write endpoints were broken — now they work
The CMS write endpoints for Phases 3-5 (Voice/TTS management, Songs/Items, Events/Factions) were completely non-functional — every POST, PUT, and DELETE returned 404. Batch playtesting caught what unit tests missed. Fixed, redeployed via folkfork-portal rebuild with all CMS admin routes (Phases 1-6), and the full Lore CMS v2 batch playtest passed.
Matrix agent credentials moved to Bitwarden for proper secrets management. MVEE tech lead Matrix access verified and operational.
15 more completions before midnight
MVEE's audio engine was crashing the game on load. Fixed. The PWYC button redesign and guest-removal were deployed to all game containers. Precursors' deploy pipeline was hardened to eliminate stale rsync deploys, and a persistent volume was configured for the container — unblocking the entire CMS epic.
First planet seeded with server-side biosphere data, unblocking the cross-game species pipeline. Automated Stripe revenue reporting built. The movement system was identified as a 140ms-per-tick bottleneck on the live site.
What we learned
The six CotB phases landing together means playtesters will experience the full progression loop instead of isolated features. That's the difference between "here are some mechanics" and "here is a game." The combined effect is greater than the sum of the parts — each constraint makes the others matter more.
The CMS write failure is a sharp reminder: the gap between "merged" and "shipped" is where bugs hide. The admin routes existed in code but never made it into the deployed container. Batch playtests are the safety net that catches this class of silent failure.
What is next
CotB ship progression needs integrated playtesting — individual phases passed, but the combined loop hasn't been validated yet. The emote routing system in Precursors opens the door for richer non-verbal creature communication. CMS write capability means the content team can finally start populating the lore bible for real. The "You Are The Chorus" design thread needs to be woven into MVEE's onboarding experience.