The one power that had to break the save
We had given ourselves a hard rule about saving. The file should remember what you did, never the state your deeds produced — keep the recipe, cook it again on load. Power after power kept that rule and shipped without ever touching the save format. Blessings were the single exception: the one god-power, out of all of them, that forced the format to change.
That deeds-not-state architecture — a save built from an ordered diary of your actions, with the present re-derived from it on load — is a sibling’s story, and it tells the principle in full: remembering what you did, not what it did. What this post follows is narrower and, to me, more interesting: when you hold yourself to that rule across a whole set of new powers, three of them keep it almost for free — and exactly one of them can’t, no matter how you arrange it. This is about the one that can’t, and why its inability is structural rather than a failure of cleverness.
Three powers that stayed save-neutral
Through the run of divine verbs we built — regenerate your energy, seed a founding pair, touch the weather, bless a single life — the question we asked each one was the same: what does this cost the save file? The first three answered, in three different ways, nothing.
Energy never gets written down at all. Your remaining budget is just your opening allowance minus the cost of every act in the diary, recomputed from scratch whenever it’s asked for, so a reload lands on the identical figure with nothing new to store — how that stays reproducible to the byte is its own story. Seeding a founding pair needs no special note either: the two creatures you place are already part of the saved world, read back whole like every other living thing, so the pair returns because it was saved — not because the act is replayed.
Weather is the most elegant case of all. Rain, calm, and frost are recorded as plain entries in the diary, and the live effect is rebuilt fresh on load as a pure function of what you asked for and how long ago — there is no running tally of an active nudge to preserve. Calming a storm goes further still: it never edits the stored weather schedule at all, it just quietly dampens the storm’s contribution at the moment the world is asked what the sky is doing, so the saved weather stays byte-for-byte the same.
Three powers, three ways of needing nothing new on disk — re-derived, already-saved, recomputed. Each was deliberately shaped to keep the format frozen. And then there were the blessings.
What a blessing actually leaves behind
A blessing is different in kind from every other verb, and the difference is the whole post. The other powers either change the world in a way you can replay, or produce an effect you can recompute from when-and-where. A blessing does neither. It leaves a lasting yes-or-no fact stamped onto one specific individual: this creature is shielded from death, once; this sapling is marked to grow faster, once. (What those two gifts mean to a player, and why a mercy has to run out, is the warm sibling’s to tell: a blessing that spends itself on one life.)
The shield is a one-time stay of execution: the rule that decides when a creature dies spends the shield instead of killing, and the creature lives — exactly once. The mark is a one-time burst of growth that clears itself the first time the plant advances a stage. What matters for the save is the gap between when the fact is set and when it is spent. You can bless a creature tonight and reload a dozen times before anything tries to take it; you can mark a sapling that then sits half-grown for a long while before crossing into its next stage. The promise has to survive all of that, sitting unspent on one life.
Why it can’t be re-derived
Here is the structural part. A weather nudge is a pure function of its diary entry plus the clock; an energy balance is arithmetic over the diary. Both are fully determined by things that are already in the save. A blessing isn’t.
The diary records that you cast a blessing, and when. But whether that shield has been spent yet — whether the next death has already come and gone, or hasn’t — is not a fact about your action. It’s a fact about the world that unfolded afterward, on its own clock, in a corner you may never have watched. You can’t reconstruct “is this creature still shielded?” from the list of things you did, because the answer depends on what the simulation did with that creature in the interim. The promise is a new, durable property living on an individual, which the world later reads and consumes.
A deed you can replay. A consequence you can recompute. But a promise sitting on one life, waiting to be spent — that you simply have to remember.
So a blessing is exactly the thing the deeds-not-state architecture can’t absorb: state that isn’t derivable from the diary. The shielded-or-not and marked-or-not flags became new fields stored with each creature and each plant in the saved world — two small facts the file had never carried before — and the save format had to change to make room for them. It was the only power in the whole set that did. The other three re-derived their way around a break, on purpose. Blessings broke the format precisely because what they record is durable per-creature truth, not a deed in a list.
Breaking it carefully
We don’t change the saved format lightly. A world in The Long Watch is a single rolling file you’ve spent evenings in, and every change to its shape is a real cost — an upgrade step to write, an old world to prove still opens. How that format grows without ever orphaning an old save is a sibling’s subject: a ladder a world can always climb. The point here is that we treat a format change as something to earn — which is why three powers went out of their way to avoid one, and blessings only took one because the alternative didn’t exist.
When it did have to happen, we made it the gentlest break we could. The change was additive: older saves load cleanly, and the two new flags simply default to off — an un-blessed world arrives un-blessed, losing nothing, because there was never anything there to lose. And it wasn’t allowed to slip in quietly: a step that alters how every world is stored is a deliberate, signed-off act, gated so it can’t happen by accident in the middle of a feature.
One more care, because it’s the kind of thing that bites: a blessing is recorded in exactly one place — the durable fact on the creature or plant — and never also reconstructed from the diary on load. Record it twice and a reload could apply it twice; a reprieve is meant for one death, not one-and-a-bit. (The hard-won lesson about powers actually surviving the save-and-load round trip belongs to an earlier verb’s bug: the power that reset itself on load.) Both blessings are otherwise plain, deterministic writes — no dice — and a world with no blessing active is left bit-for-bit unchanged.
The exception that proves the rule
It would be easy to read the blessing’s format change as the one place the discipline slipped. It’s the opposite. The whole point of holding the deeds-not-state line across power after power is that when something finally won’t fit, you know the break is real and not laziness. The inverse week — an entire emotional core built without the format moving once — is told next door: no save break. This is its mirror image. Three powers proved how far you can carry a frozen format by re-deriving everything you can; one power proved where re-derivation genuinely ends — at a lasting mark made on a single life, that the living world will only spend much later.
And that, underneath the plumbing, is the part that mattered. The first three powers touch the world and leave no trace the file has to keep. The blessing is the first time a god’s gesture writes a durable mark into one creature’s life that the world is then bound to remember — so it’s the first one heavy enough to be worth changing the save for. You don’t win here. You tend — and when your mercy actually costs something and actually sticks, the file has to hold it.
