Sickness travels in the meal
We could have written a separate plague for every way a creature can fall ill. Instead we built one sickness — and the most interesting thing it does, crossing from a hunted animal into the hunter that eats it, is something we never actually wrote. It simply falls out of rules the world already had.
This is the story of that one quiet design choice, and of the conviction underneath it: that the food chain in The Long Watch should be a system you reason through, not a set of disconnected switches. A sickness that travels in the meal is what that conviction looks like when you follow it all the way down.
One sickness, not a catalogue
The tempting way to build disease is one plague at a time — a hand-authored illness for the grazers, another for the hunters, a third for the birds, each with its own numbers typed in by feel. That way lies a wall of bespoke cases, and a world where every new way to get sick is something we had to think of first.
We took the opposite path: a single illness model that any creature can move through, the same shape for a rabbit and a fox alike. It needs no hand to place it and no trigger to begin — a sickness sparks on its own and walks each creature through four states, well to carrying to contagious to recovered, and what an outbreak does once it is loose is its own story. What this post is about is the one route between creatures that we never actually wrote down.
The jump we didn’t write
Here is the part the post is named for. When a predator kills and eats prey that was carrying the sickness, the predator can catch it. The parasite rides up the food chain inside the body of the eaten animal. A hunt becomes a route for disease.
What we want to be honest about is that we did not script that pathway. There is no special rule that says when a fox eats an infected rabbit, infect the fox. There is one transmission model, and there are the kill-and-eat rules the world already had from when we first let a creature eat. The prey-to-predator jump is what happens when those two meet. It is an emergent consequence, not a case we enumerated — and that is exactly the kind of thing we were hoping for.
We were careful about one boundary, though. The exposure only reaches a predator that was genuinely in range of the kill — the one that actually did the eating. The chain of infection follows the real act of the meal, not mere nearness. A bird passing overhead doesn’t catch it from a carcass it never touched.
A parasite in prey can infect the predator that eats it — not because we wrote that case, but because a hunt was always a meal, and a meal is how the sickness moves.
A chain you reason through
The reason the jump can fall out so cleanly is that the whole food chain is built as one connected loop rather than a row of independent levers. Sickness doesn’t get its own private machinery; it simply takes its seat in the single place that weighs how likely any creature is to die — a slow, accumulating push toward the end whose ranking among the faster ways to die is its own story.
Because everything routes through that one loop, a change in one corner ripples honestly into the others. Sickness deaths thin a population. A thinner population shifts what a predator finds to eat. That shifts how often things breed, which shifts how many animals the land can carry. None of that is choreographed. It is the consequence of letting one system feed the next instead of pretending each lives in its own box.
Your flock isn’t exempt
There’s a temptation, in a god game, to quietly protect the things the player has bonded to — to make a creature you’ve been following somehow above the rules. We didn’t. A line you tend is part of the chain like everything else. A shepherd’s animal can carry the sickness, can pass it on to the herd around it, and can die of it like any wild thing.
That isn’t cruelty for its own sake. It’s the whole point of tending. If your flock were immune by virtue of being yours, then watching over it would mean nothing — there’d be nothing at stake to watch. Tending doesn’t lift a creature out of the world’s rules. It just means you’re the one who’s there, paying attention, when the world applies them.
And so far, nothing is sick
Now the honest part. We built this entire machine — the four states, the travels-in-the-meal vector, the derived character of each illness, the recovery-and-immunity curve — and, like the outbreak system it lives inside, shipped it switched off until the balancing pass. The structure is fully present in the world, and nothing actually gets sick yet.
That sounds odd until you say why. The hard part of disease isn’t the wiring; it’s the feel — how often an outbreak should start, how fast it should spread, how dangerous it should be before it stops being a quiet pressure and starts being a tragedy. That is a balancing question, and balancing by feel is its own deliberate pass, not something to rush in alongside the plumbing. So we put the bones in place, proved they’re sound and harmless, and left the dial for later.
The goal we set ourselves for this whole effort was a plain one: an outbreak that arises on its own, spreads, abates, and that the player can meaningfully bend with their own hand. A proof run showed all four — including that a single blessing, a touch that breaks a fever, measurably changed how the outbreak ran. Whether it does so in your world is a dial we haven’t turned yet. When we do, sickness will already know how to travel — we just have to let it.
