The one thing a save can’t rebuild: a population no seed can bring back
A save in The Long Watch is deliberately lean: it writes down only the things the game can’t rebuild on its own — and almost nothing qualifies. The land regrows from its seed, your deeds replay in order, the seasons and soil recompute from the clock. This is the story of the single exception, and of teaching a save to keep the one thing a load can never bring back.
The rule a save has always kept
From the very first world, a save has followed one rule: store only what can’t be recomputed. It is why a saved world is so small. We don’t write the terrain down voxel by voxel — on load it regrows from the world’s seed, hill for hill. We don’t photograph the world your godly acts left behind either; we keep an ordered diary of the acts themselves and re-do them, so the shape you carved comes back because we remember the deed, not the state it produced. Even reopening a tended world eventually learned to ask for a light read instead of rebuilding ground it didn’t need. Anything derivable is left out and reconstructed. A save stays lean because the world can be rebuilt.
The exception that proves it
There is exactly one place this rule breaks, and it comes from the far edge of the world. Past the last watcher, the game stops tracking animals one at a time and keeps each far population as a compact summary instead: a head count, the average of its traits, and how much they spread. Life out there is folded from a crowd of animals into a single population that lives on as a number — one that goes on growing and quietly drifting into something of its own. Those are their own stories. What matters here is a consequence of how such a summary is made.
To fold a crowd of animals into a summary, you discard the animals. That is the whole point — it’s what makes a distant wilderness cheap to keep alive. But it is also irreversible. The seed fixes where a population started; its drift, though, is the sum of countless tiny random steps taken over seasons no one was watching, and once the animals that walked those steps have been folded away, nothing remains that could retrace them. The land can be regrown from its seed. This can’t.
Everything else in a save can be recomputed. A drifted population is the one thing that can’t — once its animals are gone, only the summary remembers where they’d wandered.
So the summary itself becomes the one piece of a living world a load can’t rebuild — and therefore the one genuinely new thing a save has to actually keep. It isn’t quite the first time the file had to grow for this reason: a single god-power — a blessing — once forced the format to change because its effect couldn’t be re-derived either. But a blessing is something you did; a drifted population is something the world did on its own, while no one was looking.
Landing it in two careful steps
We added it in two deliberate steps, and kept them apart on purpose. First we taught the save file where to put these summaries — a place for them in the file — and proved, in isolation, that a summary could be written out to disk and read back intact, unchanged by the round trip. That was finished and checked entirely on its own, before any of it touched the running game.
Only then did we connect it end to end: when you save, the world’s live summaries are captured into the file; when you load, they’re restored back into the world exactly as they were. Two small pieces, in order — prove the storage in the quiet, then wire it to the world — so that if the second step had gone wrong, the first was already known-good and the fault had nowhere to hide.
Two details that keep it quiet
Adding a new kind of saved state to a game people are already tending is the sort of change that can go wrong silently, so two rules guard it.
The first is that a summary is only written when it actually holds something. An empty one — or a world that has never folded a single population — writes nothing at all. A save from such a world comes out byte-for-byte identical to a save made before any of this existed; the change is, to that world, invisible. Older worlds simply carry no far-population state and open exactly as they always did — the same forward-only spirit that lets every old save climb to the current shape.
The second is subtler. A summary that still stands for a living population is preserved even after its individual animals have been shed — because that aggregate is precisely the irreplaceable part. It would be a quiet catastrophe to mistake an emptied-out roster for an emptied-out population and let the summary lapse. The animals being gone from memory is exactly why the number has to stay.
The lives we never fold
One kind of life is held out of all of this. The creatures you shepherd and name are always kept as full individuals — never folded into a neighbouring summary, always saved and loaded as themselves. That guarantee is the emotional heart of the game and has its own story; here it’s enough to say the save treats a life you’ve chosen to follow as exactly that — itself, all the way through, across every close and reopen. The folding is for the anonymous far country, never for the one you’re keeping.
Built now, so the first save can’t lose it
There’s one more thing worth being honest about: the far-off population tier still ships switched off. None of this runs in a world you can play today. The sickness system did exactly this — built in full, its two irreducible facts stored, then switched off. So why finish its save support first?
Because the alternative is worse. If we waited until the day the tier is turned on, the very first save made after that switch would be the first ever asked to carry a drifted population — and if the file didn’t already know how, that save would silently lose it. The drift would be gone with no error and no warning, just a far world that had quietly forgotten who it had become. Building the persistence now, and proving it round-trips before the feature is ever enabled, means the ground is already laid the day the tier wakes up. Before release we’re free to grow the shape of a save as much as we need — nothing shipped depends on today’s format — so the honest move is to add the new kind of state cleanly, in advance, rather than bolt it on under pressure later.
Almost everything in this world is a recipe: hand the game a seed and a diary of what you did, and it cooks the world back. That is what lets a save stay small and a world stay faithful. But a wilderness left to itself becomes something no recipe anticipated — and the least we owe a world that has quietly grown into its own is to write that one thing down. You don’t win here. You tend. And a world worth tending is one that remembers even the parts of itself you never watched happen.
