Remembering what you did, not what it did
A save in The Long Watch does not store the world. It stores the things you did to it. That one decision — remember the deed, not the state it left behind — has carried the whole project a long way. But the moment we added new ways for a god to act, it became a question we had to answer three times, differently each time.
Here is the shape of the thing, stated plainly, because everything below is a consequence of it. When you save, we don’t write down the hills as they currently sit, or the soil as it’s currently enriched, or how much power you have left. We write down your actions — each one stamped with the in-game moment it happened, in the order it happened — into a single running log of deeds. When you load, we start the world fresh from its seed and re-do those deeds in order. The world you left comes back not because we photographed it, but because we kept the recipe and cooked it again.
That the rebuild lands exactly where you left it — the same hills, byte for byte, even on a different machine — is its own story, and a sibling post tells it: a forest allowed to surprise us, a save that never is. What I want to follow here is narrower and, to me, more surprising: that “re-do the deeds” turns out to mean three different things, and getting them confused would have quietly broken the world.
Why the same rule needs three answers
The work that forced the question was a run of new divine acts — the first real verbs a player-as-god gets. Reshaping the land. Calling life into being. Touching the weather. They feel like one category — “things you do to the world” — and they all ride the same spine underneath: every act is checked against your energy, charged for it, and written into the one log. But when you ask each of them what happens when you reload?, they answer completely differently.
“What you did” and “what the world looks like now” are not the same thing — and a save that stores the wrong one breaks the world.
The land: replay it
The four sculpting verbs — raise the ground, lower it, soften a slope, roughen it up — are the case the whole principle was built for. The terrain is never stored directly. On reload it is rebuilt from its seed, fresh, exactly as it first generated. So the lumps and hollows you carved by hand would simply not be there — the world would come back as if you’d never touched it.
The fix is to stop trying to save the shape and save the acts instead. Every sculpt is an entry in the log; on reload they’re replayed, in order, onto the freshly-rebuilt land, and the shape returns. The roughen verb is the subtle one: it scatters small random bumps, and if those came from ordinary randomness the replay would land somewhere slightly different every time. Instead it draws from the world’s own seeded source — the same deterministic stream the terrain itself comes from — so replaying the act produces bit-for-bit the same bumps. You get back the exact hill you made, not a near miss.
The founders: store them
The second verb makes life rather than landscape. Seed releases a founding pair — two adult creatures of a species you choose, set down near where you’re looking, just close enough that they can later find each other and breed. It’s the first act that creates beings, and the save question flips on its head.
Creatures are part of the saved world. The whole living population is written down and read back whole — that’s how the animals you weren’t looking at survive a reload at all. So a founding pair needs no replay. The two animals come back because they were saved, like everything else alive. We still log the act — more on why in a moment — but the effect, the pair, is never re-run.
The sky: recompute it
The third set touches the weather: summon rain, calm a storm, push back frost. These don’t permanently change anything. Each is a soft, region-shaped influence that swells up, lingers for a finite window, and fades — a nudge to the temperature, a patch of extra rain, a hush laid over a storm. Calm a storm is gentle in a deliberate way: it never deletes the storm from the schedule, it just quiets the storm’s contribution for as long as you’re asking, then lets it back.
Because each of these is a pure function of where and when you cast it and how much time has passed, there is nothing to store and nothing to replay. On reload we recompute the influence from the same logged when-and-where, and it picks up exactly where the clock says it should be — already faded if enough time has gone by, still swelling if not.
So: three acts, three answers. A founding pair becomes part of the world and is stored with it. A reshaping of the land is replayed onto fresh terrain. A passing storm-calm is recomputed from its when and where. One log, one cost-and-ledger spine — and three different relationships to the save, each chosen to fit what the act actually is: a thing, a change, or a fleeting influence.
The bug that almost wasn’t
The sharp edge that made all of this worth writing down lives at the seam between “store” and “replay.” The replay-on-reload step walks the log and re-does the deeds. If we’d let it re-do every deed, a saved-and-reloaded world would have grown the founding pair twice — once because the creatures were saved with the population, and once again because the Seed act sat there in the log waiting to be replayed. Two foxes would have become four. A phantom second pair, every reload.
What prevents it is a small, firm rule: the replay step re-runs only the land-shaping acts and deliberately passes over everything else. The Seed act and the weather acts ride in the same log — they have to, for their cost — but they’re skipped on the way through. The discipline turned out to be exactly that: knowing, for each act, whether the world already remembers its result, and replaying only the ones it doesn’t.
Which is why we log even the acts we never replay. The log is also how we re-derive your remaining energy (its own story, power you have to spend), so the act has to stay even when its effect is skipped. Drop the Seed act from the log to avoid the double-spawn and you’d get the animals right but the energy wrong: you’d be refunded for life you actually paid for. So the act stays; only its effect is skipped.
The deeper bug underneath
Wiring up replay flushed out something older and quieter: the log of your deeds was written on save but never read back on load, so every reload replayed an empty history — a leak with its own story, the power that reset itself on load. The point that belongs here is the lesson it left behind.
That’s the lesson we keep relearning and will keep relearning: a “this works” claim has to be proven on the real save-and-reload path, not reasoned about. A save that remembers what you did is a lovely idea right up until the moment you forget to read the diary back.
There’s a softer reason all of this matters, and it’s the part the architecture quietly serves. The world is meant to remember — not as a snapshot, but as a record of the moments that mattered while you tended it. A save built from deeds rather than states is the technical spine under that promise. You don’t win here. You tend — and the world keeps the diary.
