PUBLIC BUILD LOG
What changed.
Why it matters.
A concise, player-facing history of live Beta updates. Internal refactors stay out; changes to progression, balance, saves and decisions stay in.
RELAY//ZEROPRIVATE INFRASTRUCTUREBETA
What changed.
Beta 0.9.4 · Public relay
The first public release candidate is wired for relayzero.net.
- Added the official domain, link previews, sitemap and index controls.
- Hardened the Cloudflare Pages shell with security headers and a real not-found route.
- Fixed offline navigation so FAQ, Changelog, Legal and the game keep their own cached responses.
- Connected voluntary support without adding accounts, tracking or in-game purchases.
Beta 0.9.3 · Relay Zero
The project has a permanent identity and a clearer return loop.
- Renamed the game to RELAY//ZERO and introduced the new visual mark.
- Made Offline Queue capacity visible on Command and the landing page.
- Replaced the technical “swapping” label with the clearer Queue Overload consequence.
- Added searchable, categorized FAQ and this public Changelog.
- Added save-key migration, preserved backup data and protection against newer incompatible schemas.
Beta 0.9.2 · Stronger first impression
The opening now states the fantasy and core loop more directly.
- Reworked the landing message around one old machine, automation and compounding growth.
- Improved the cockpit hierarchy, progressive navigation and unlock notices.
- Expanded system identity through upgrade tracks, Research and multi-run caps.
Beta 0.9.1 · Decisions before breadth
Systems were compressed around clearer ownership and consequences.
- Moved System Health into the persistent rail.
- Combined Operation setup into target plus risk, then automatic resolution.
- Added Pause Contracts as the explicit way to reserve capacity for Operations.
- Converted Cold Reboot into one Relay Doctrine decision with permanent lessons.