Storms that are already on the calendar
When a world is born in The Long Watch, its weather isn’t decided moment to moment. Its storms are already written down. From the world’s seed we roll out a long calendar of them, stretching years ahead — and that calendar is fixed for the whole life of the world. A storm is on the books before you ever see its first cloud.
This is the story of that calendar: why a world’s weather is settled in advance rather than improvised, what that lets us ask of the sky, and why a thing that sounds like a shortcut turned out to be the most honest way to make a world you can trust to be the same place every time you return to it.
A companion piece is about the feel of that weather — how rain belongs to a place, how each climate has its own temperament, how a storm drifts in from somewhere rather than blinking on across the whole map. That’s its own story. This one stays with the calendar underneath it.
Each entry on that calendar is a storm laid down whole from the seed — a moment, a place, a duration, a fierceness, a reach — so the storm that arrives on a given afternoon is the same storm, every time that world is played. The storm itself, its center and the soft edge it fades across, is its own story; here we stay with the list it’s written on.
Asking the sky about a moment that hasn’t happened yet
The weather you can ask for — rain, wind, temperature — is derived, not stored: each is read on the spot from the calendar and the climate rather than kept in memory. The quietly radical part is what writing the future down lets us not do. Because the calendar already reaches years ahead, the world never has to play out the minutes between now and then. We can ask it a direct question — what is the sky doing at this place, at this moment, even one well out in the world’s future? — and get the answer straight back.
To answer, the world simply walks the calendar: it picks out which storms are active at the moment you asked about, measures how strongly each one is felt at the exact spot you asked about, and adds them up. No clock has to have ticked. A storm three seasons away is just as answerable as the rain on your face right now, because both are entries on the same list.
We don’t wait for a storm to arrive to know what it will be. It’s already on the calendar — we just read it off.
Storms arrive the way real weather does
A calendar could feel mechanical — a storm every so many days, like a metronome. Real weather doesn’t do that, and neither does ours. The gaps between storms follow a natural bunching pattern: storms cluster and then thin out, arriving unevenly the way weather actually arrives, while still averaging out to a known rate over time. A stretch of grey days can crowd together; then a long fair spell can open up. None of it is random in the sense of being unrepeatable — it’s the same uneven rhythm, drawn the same way, for the same world, forever. That known rate is tuned per climate — which is how each kind of world ends up with weather of its own character — but the temperaments themselves live in the companion piece; here it’s enough that the calendar gives each climate its own cadence.
How far ahead to write
There’s a real question hiding in “roll out the future”: how much future? We settled on rolling the calendar out about three in-game years ahead at world birth — far enough that a long stretch of play never runs off the end of it, but bounded, so creating a world stays quick. For a typical world that’s a few dozen storms penciled across those years (the companion piece counts them off for one example world): a quiet, legible weather future, the same on every replay.
And we left ourselves a back door. If three years ever proved too costly to lay down up front, the horizon can be shortened without losing anything, because the same machinery that walks the calendar can keep walking it forward on demand and answer a question even further out than we’d written ahead. The precomputed stretch is an optimization, not a limit — the calendar is, in principle, endless, and it’s the same calendar however far you read.
A promise like that is only worth as much as your ability to keep it through months of changing the game underneath it, so the calendar’s opening stretch is one of the things we hold to byte-for-byte reproducibility — guarded so a future edit can’t quietly nudge the weather off without our knowing. That guard, and the wider discipline that keeps a living world the same world on every replay, is its own story.
Why a fixed future feels like freedom
It can sound, at first, like the opposite of a living world: every storm decided before you arrive, the weather laid out like a railway timetable. But the fixedness is what lets the rest of the world breathe. Because the sky always answers the same way, every system that leans on it can lean without worrying — the soil reading the rain, the look of wet or frosted ground, the slow wearing of a riverbank — and none of them ever drift out of step with each other or with what you saw.
And it’s why a caretaker’s later power over the sky could be gentle rather than godlike. When you ask a storm to be calmer over the place you love, you don’t erase it from the calendar — the world had always planned to send it, and it still does; you only soften how hard it’s felt, there, for a while. The timetable stays intact, so the same world stays the same world. That — asking the sky gently rather than commanding it — is its own story.
The thing we’re proudest of isn’t any single storm on the list. It’s that a world’s whole weather future is settled, honestly, from the moment you first tend it — penciled in, knowable, reachable, and the same on every return. You don’t win here. You tend. And the weather you tend through was, quietly, always going to be exactly this weather.
