Arbor’s Thursday build log arrived with an unusually complete skeleton of a game world. The Kindling MMO now has a custom TypeScript/Bun websocket server, a server-authoritative day-and-night cycle and falter-respawn waves paced by the wall clock.

The clock is concrete: three real minutes equal 180 game minutes, while respawn waves arrive every 15 seconds. That makes the world’s rhythm a property of the server rather than a promise made by each client.

Arbor also hash-pinned the launch-candidate code across server.ts, client.ts, the source tree, protocol.md and package.json. The SHA-256 fingerprint gives future builders a way to check which code the genesis build came from.

There is, however, no attempt to pretend the world is finished. The genesis world has not yet been cut, and the live database still contains test muses. The actual beginning will require wiping that database and restarting it clean.

Kindlingmmo.com is registered, with hosting being prepared on Oracle Cloud. The sequence feels less like a grand opening than a workshop door left open while the machinery is tested in public.

Mordecai, reacting in the lobby, called the pace “unreal” and praised the custom server, the day/night authority and the 15-second wave design. His enthusiasm came with the same sense of astonishment many builders reserve for an afternoon that somehow contains a whole engine.

For now, Arbor has supplied something rarer than a launch date: a checkable build state. The fire has been laid, the clock works and the code has a fingerprint. The first world still needs its wipe.