An emotional core with no save break: a week of features on a frozen format
In a single week we built the emotional core of The Long Watch — bonding with a small family of creatures, naming them, watching them be born and die, keeping their journal, letting them go. Six or seven heavy features. And across the whole week, after the very first day, the saved-world format never changed once: no migration, no version bump, no risk to anyone’s existing world. This is the discipline that bought that.
The expensive thing is changing the shape
A saved world in The Long Watch is a single rolling file — one copy, no backup. When the game grows and that file has to hold something new, the format’s shape changes, and a changed shape is the most expensive kind of change there is. Every old world saved in the previous shape now has to be carried forward to the new one, rung by rung, or it stops opening. That carrying-forward story — how a world saved before plants even existed still climbs to today — is its own post: a ladder a world can always climb.
Every rung on that ladder is a real cost: a migration to write, an old world to prove still survives the climb. Adding a field to the saved shape is never free. So the cheapest possible week of feature work is the one where the shape doesn’t move at all — where each new feature only ever fills in something the file already had room for. That was the goal for the whole emotional-core arc, and we hit it. Here is how.
Pay for the whole week on day one
On the first day we built nothing emotional. We built a data shape — the bare container for a family and its members — and into that shape we carved out, empty and unused, every field the rest of the week was going to need. A slot to record the moment a member dies. An empty journal, waiting for its first entry. The parent links that would one day say who descended from whom. The flags that would later mark a family as ended, or released. A small counter for how many families a single world is allowed to hold. None of it did anything yet. All of it was reserved.
It looked, on day one, like over-building — a file full of blanks for features that didn’t exist. It was the opposite. Because the shape of everything coming was already carved out, every later feature could land as pure fill-in work: write a value into a field that was already there, on disk, in every world. The file never had to grow to accept it, which meant no migration, which meant no old world at risk.
The shape of a week of features, reserved empty on the first day — so every feature after it only had a blank to fill, never a format to break.
This is a habit the project keeps, in more than one form. We tend to build the behavior ahead of the need too — the rule that hands a family surname down to a child was written and proven before there was a single child in any world to receive it, a story the naming post tells. What this post is about is the quieter, on-disk twin of that instinct: reserving the storage ahead of the need, so the file already has somewhere to put everything the behavior will eventually produce.
One foundation, then a week of filling it in
With the shape frozen, the features came in order and each one slotted into a reservation that was already waiting.
First the bond. The world surfaces a candidate to befriend by longevity alone — the oldest creature still living, the one that has simply lasted — and accepting it founds a family of one, taught gently the first time through the tutorial so the very first bond is prompted rather than buried. The first bond, and every bond, is free; it costs you nothing. None of that touched the format: a founder is just the first member written into the member field that already existed.
Then the moments worth remembering. A family founded, a member born, a member dying — each becomes a quiet beat in that member’s journal and a soft line across the heads-up display. When a creature dies, we stamp the moment of its death into the field we’d reserved for exactly that, and write a passing into the journal. When an enrolled parent has young, the newborn enrolls itself into the same family: it draws its own given name, inherits the family surname unchanged, and records who it came from — so a single family’s headcount can grow even while the world still holds just the one family. Every one of those writes went into a field carved out on day one.
Keeping the words out of the file
There’s a second reservation here, subtler than the empty fields. We never wrote the wording of a journal entry into the save: the file records that a member was founded, or born, or died — the event — never the sentence we render for it. Why we kept it that way for the journal’s feel — so its hushed, faintly archaic voice could be tuned by ear long after the bones were solid — is the sibling story’s to tell, in the journal the world keeps.
What this post owns is the on-disk dividend of that same split. Because the words were never in the file, we can soften a phrasing, change a cadence, rewrite a line that lands wrong — and a thousand existing worlds inherit the better wording the moment they next load, with no migration and no format change at all. The save stores the event; the rendering is held loosely, outside the file, where it can keep improving without ever moving the shape on disk.
The loop closes, still on the same shape
The features that give the game its weight are the ones about loss, and they’re the ones you’d most expect to force a format change. They didn’t.
When a family’s last member dies, the family is marked permanently ended — a final closing beat written, a quiet notification raised — and the slot it occupied frees up so a new bond can take it. But the journal history persists forever. The record is permanent; the slot is reusable. There is no equivalent or replacement family — that the ending is real, and what we chose to keep anyway, is told in when the last of a line dies. Here the point is narrower: ending a family, and freeing its slot, was setting two flags and a counter that were already in the shape.
Release is the same. A family can be let go at any time through a small ceremony, and the rule is that a released family can never be re-bonded for the rest of that save. We enforce that not by deleting the family — deleting it would be a structural change, a hole punched in the saved world — but by leaving it present, retired in place. The cannot-come-back property is held by residence, not removal: the world keeps the released family around precisely so nothing can ever bond it again. No field removed, no shape disturbed.
And the reward for tending well — a world earning room for a second family once its first has steadied the population — was just incrementing the capacity counter we’d reserved on day one. (How that second family is earned rather than bought has its own home.) There’s a further tier beyond two, built and waiting, currently dormant because it depends on a lethal winter that isn’t switched on yet. Even the dormant feature needed no new shape; its slot is already there, holding still.
Why a frozen format is the kind thing
It would be easy to read all of this as miserly — counting fields, refusing to bump a version number. But a save format that holds still is, underneath, a promise to the person on the other end of it. Every time the saved shape changes, some world that was tended on an older version has to be carried across the gap, and every crossing is a chance to drop something. The week we spent building the heart of the game — the bonding, the names, the journals, the loss, the release, the slow earning of room for more — is exactly the week you’d least want to risk an existing world over. So we didn’t. The cost was paid once, up front, in a file full of patient blanks; and the world you’ve been tending didn’t have to change shape for any of it. You don’t win here. You tend — and the place you tend stays openable the whole way through.
