The quiet moments between encounters

Shock is the weakest tool on a phone

Gore in a zombie game is doing two separate jobs. One is feedback — confirming a hit landed and a thing is finished — and that one has a replacement we have written about at length. The other job is shock, and shock is the one it does badly on mobile even before you remove it.

A phone screen is small, it is very often silent, and it is frequently being looked at somewhere public. All three work against a startle. The image is a few centimetres tall, the audio that was meant to carry it is muted, and the player is not going to react in a way they would be seen reacting on a bus. A mode built on shock loses most of its effect to the venue.

Anticipation has none of those problems. Dreading a thing that has not happened yet works at any screen size and needs no sound at all, because it is running in the player's head rather than on the display. So Deadwood Quarantine is built almost entirely out of anticipation, and the machinery that produces it is a clock.

Five seconds is the whole warning

A raid announces itself five seconds before it lands. That is the entire notice, and it reads as generous until you put it next to the map: the island is 480 metres from the wall to the far shore. Five seconds does not get you back to the bridge from anywhere on it worth being.

What five seconds does buy is exactly one decision. Pick a door, finish a reload, or accept where you happen to be standing. It is long enough to act and far too short to solve, which is the precise window where a player feels responsible for what happens next without being able to avoid it. A longer warning would turn every raid into a retreat, and a shorter one would make the outcome arbitrary.

The first raid lands forty seconds into a run, before anyone has settled. After that the interval is knowable and the moment is not, which is the right shape for a recurring threat: you learn the rhythm, and learning it does not save you.

Eight seconds of quiet

The cadence is not fixed. It comes off the same single value everything else in the zone comes off — how far west of the wall you have walked — and it travels a very long way between the two ends of the island.

Three numbers move together, and the third is the one that does the work. How long a raid runs. How long the gap is before the next one starts. And, at the top of that gap, the lull: a window where nothing arrives at all. The lull is the only stretch of a run where you can reload, board a door and pick things up off the floor without something walking into you while you do it — the game announces it, in those words, as the street going quiet.

Near the wall

A raid runs about 32 seconds. Then 115 seconds before the next one starts, the first 12 of which are the lull.

Deep in the zone

A raid runs 58 seconds and the gap to the next is also 58. The lull inside it is 8 seconds.

The curve is in the ratio, not the headcount

Read those two rows as proportions rather than as durations. Near the wall a raid is about a fifth of your time and the rest of it is yours. Deep in the zone the raid is 58 seconds and the gap is 58 seconds, which is an even split — half of everything that happens out there is a raid. You stop surviving raids with pauses in between and start taking pauses in between raids.

The lull is the sharper cut, and it is the one you feel. Twelve seconds is enough to reload, cross to a door and get boards on it. Eight is enough to do one of those, and you have to choose which — that is the difference between a defence you prepare and a defence you improvise, and it costs four seconds.

That inversion is the whole horror design, and it is delivered entirely through timing. Nothing about it is gore, and nothing about it needs a screen bigger than a hand or a single second of audio. It is arithmetic the player feels rather than reads.

It is also self-inflicted, which matters more than it sounds. Nobody set the raid clock on a difficulty screen. A player walked there, one step at a time, watching the pay go up.

The exit stays open, and that makes it worse

There is a school of horror design that locks the door. Deadwood does the opposite: the infected leash to the island and cannot follow anyone onto the bridge, so retreat is available at every second of every run.

That should defuse the tension, and it does not, because it relocates it. When the exit is locked, staying is the game's decision and fear is something being done to you. When the exit is open, staying is your decision, and every raid you sit through is one you signed for.

It also means the mode never has to be graphic about the consequence. The consequence is a choice you already made — and at the deep end the raid clock puts it back in front of you about every two minutes.

The stake is a number, and the number is not red

What a run can cost you is money and only money. Hazard pay accrues by the minute and multiplies with depth, every infected you contain pays a bounty on top, and none of it is yours until you cross the bridge. Go down inside the wire and the unbanked packet stays there.

This is the part of the no-gore argument people usually miss. A zombie game normally shows you the cost of failing, in some detail. This one prices it instead. The figure in your pocket is the horror instrument: it climbs while you stand there, it is the only reason you are still standing there, and it is deleted if you misjudge the walk home.

So a whole run reads off two numbers — how deep you went, and how much you are carrying. Neither of them is red, and neither of them needed to be.