The save that remembers who was sick
Most of The Long Watch never needs saving — hand the world its seed and the record of what you did, and it rebuilds itself faithfully. Disease was the first thing that didn’t fit. It forced a sharper question than the one we usually ask about saving: not “will this break the file?” but “what is the file actually responsible for carrying?” The answer turned out to be exactly two facts.
We’ve told the story of what a save in this game is — that it records your deeds and re-cooks the world from them on load, never a photograph of the state your deeds produced. That principle is a sibling’s, told in full: remembering what you did, not what it did. This post is about a different and, to me, more interesting question that disease dragged into the open. Given a world that can rebuild almost everything from first principles, what is left that the save must remember — because nothing else can reconstruct it?
Two questions that look alike and aren’t
It’s easy to fold this into the question we ask whenever the game grows: will adding this break old saves? That one is about not betraying worlds you’ve already written — carrying every old file forward so it still opens, the migration-ladder story a sibling owns: a ladder a world can always climb. But disease asked something prior to that. Before you can worry about breaking a save, you have to decide what the save is for — which facts about the world it is on the hook to carry, and which it can cheerfully forget because it can compute them again.
So the work here wasn’t mostly plumbing. It was a sorting exercise: take everything a sickness touches and put each piece into one of two bins. Forgettable, because the world can rebuild it. Or irreducible, because nothing the file already holds can reconstruct it, so the file has to remember it itself.
What the world can rebuild on its own
Almost all of an outbreak lands in the forgettable bin, and that is the happy part. The faint background chance that a sickness simply flares up; how it spreads from one creature to a neighbour; the way it can ride up the food chain inside a meal; how readily each kind of animal catches or shrugs it off — all of that is rule and rate, the same in every world, recomputed from the seed every time. The shape an outbreak takes — rising, cresting, and abating as survivors recover — is a sibling’s subject (the shape of an outbreak), and none of that shape needs a single byte on disk. Hand the world the same seed and the same recorded deeds and the same outbreak grows again.
This is the same instinct that runs through the whole save: prefer to recompute. How hungry a creature is, for instance, we never store — it’s re-derived from when the animal last ate. A fact you can rebuild from things already in the file is a fact you should never duplicate into the file, because then there are two copies that can disagree. So the default answer to “should the save remember this?” is a firm no. Disease’s interest is entirely in the small set of things where the answer had to be yes.
The two things nothing can reconstruct
Here is the heart of it. Two facts about a creature, and only two, cannot be rebuilt from the seed and your deeds — and so they are the only things disease added to the save.
The first is a creature’s current place in an illness, caught mid-outbreak. An animal walks a short path when it falls ill: well, then carrying the thing quietly, then contagious, then through to recovered. Each sick creature is somewhere specific on that path right now, with its own private countdowns — how long until what it’s carrying turns contagious, how long until it pulls through. There is no formula that reproduces “this particular fox is three days from recovering” from the fox’s position, its lineage, or the day it was born. That state is the live, in-flight result of a chain of chance that already happened. If the game threw it away on save and re-rolled it on load, you would not reopen the outbreak you left — you’d reopen a different one.
The second is the immunity a survivor has earned. A creature that recovers from this sickness is immune to it for the rest of its life — permanently, with no slow fading we’d have to track. That permanence is exactly why it’s irreducible. “Has this animal already been through the sickness and come out the other side?” is a fact about its private history, not about any rule. You can’t look at a healthy creature and recompute whether it’s healthy-and-catchable or healthy-because-it-already-survived. The two look identical from the outside; only the save knows the difference.
A sickness the world forgets the moment you close the game was never really part of the world — reopen to a healthy meadow and the simulation has quietly lied about what you lived through.
That is the line the title points at. We extended the saved world to record, for every creature, exactly where it sits in the arc of an illness — its stage, its countdowns, and whether it has already crossed into lasting immunity. Not because we wanted the file to carry more, but because those were the only facts a reload genuinely could not put back on its own.
What this isn’t: the blessing’s break
It would be fair to point out that we’ve described storing a durable per-creature fact before — a blessing leaves one, and it was the single power that forced the format to change. That’s a sibling’s story: the one power that had to break the save. The kinship is real, and so is the difference worth naming. A blessing is a mark the player deliberately places and the world later spends. A creature’s illness state is something the world itself produces, unprompted, in corners you may never watch — an outbreak can take hold far from wherever you happen to be looking. One is a promise you make; the other is a wound the world is carrying. Both are irreducible, and both have to be remembered — which is rather the point. The same test sorted them: can this be rebuilt from what’s already on disk? When the answer is no, it has to be written down, whoever made it true.
Disease as one more slow way a life can end — how it’s ranked among being hunted, crowding, hunger, the cold, and old age — is the cause-of-death story, and it lives next door (causal death). What matters for the file is only this: the dying is recomputable from the rules, but the in-progress illness that leads up to it is not.
An old world opens disease-free
Sorting the facts was the design. Making the change land gently was the rest of the care. A world saved before any of this existed had no notion of illness in it, so its two new facts simply arrive empty and the save loads cleanly back into a disease-free meadow — the honest old-save-loads-clean default a sibling already tells in full. There was nothing there to lose, so nothing is lost: every creature reads back well, exactly as it was, and the world goes on as if sickness had always been latent in it and had simply never flared.
Built in full, then switched off
There’s a deliberate twist that makes the persistence work easy to misread. The entire sickness system shipped inert — every rate that governs it set to zero — so for now no creature actually falls ill, and saved worlds behave precisely as they did before. That means the new fields we added sit empty in practice, holding nothing yet. We did it on purpose, the same way the cold shipped finished but asleep: build the machine, prove it sound, and leave the question of how dangerous and dramatic an outbreak should feel for a later, hands-on balancing pass, separate from the plumbing.
Inert is not the same as untested, though, and the persistence claim is exactly the kind you can’t take on faith. So we turned the rates on in a sealed test world and ran a full outbreak through its rise and abatement — the curve’s own shape is a sibling’s subject, told above. What this post needed to watch was narrower: at the height of it, with many creatures mid-illness and others freshly immune, we saved and reloaded. Survivors carried their immunity forward, the sick carried their stage and their countdowns — and the save held both, which is the whole thing this post is about.
It would be easy to file this under “we added disease and the save grew a little.” The part worth keeping is narrower and travels further: deciding what a save is responsible for is a design act, not an afterthought. Most of a living world is reconstructible, and the discipline is to lean on that hard — to store almost nothing, and to store it only when nothing else in the world can rebuild it. A sickness pushed us right to that edge, because an outbreak you reopen has to be the one you left, and a creature that survived has to stay survived. You don’t win here. You tend — and a world worth tending is one whose save remembers, faithfully, even who was sick.
