Jensen

The Recovery Beat

· 5 min read

What Red Dead Redemption 2 gets right about slowing down, and what WoW Forever gets right about it too

Everything is supposed to be faster now. Groceries arrive same-day, videos cut every two seconds so nobody has time to click away, and the sociologist Hartmut Rosa wrote an entire book, Social Acceleration, arguing that technology, social change, and the raw pace of daily life have all been speeding up together for two centuries — and that despite it, we don’t feel like we’re arriving anywhere. He calls the result frenetic standstill: sprinting hard enough to be out of breath, standing in the same place. It wasn’t written about games. It’s hard not to think of it while playing one that refuses to hurry.

A handful of the most acclaimed games of the last decade are deliberately, almost stubbornly slow. “Slow” usually gets treated as a synonym for “padded” — filler between the parts that matter. But there’s a real design argument for slowness that has nothing to do with artistic pretension, and it’s worth taking seriously on its own terms before deciding whether a given game earns it.

Downtime is not filler

Tracy Fullerton’s Game Design Workshop treats a play session’s pacing the way a screenwriter treats a story’s tension: it should rise and fall in a curve, not sit flat and not climb in one unbroken line. The low points in that curve aren’t dead space — they’re what make the high points register as high. A game that never lets up doesn’t feel more exciting for it; it feels exhausting, because there’s no baseline left to rise from. Fullerton has designers sketch this out directly, as a literal graph of intensity over time, precisely because it’s easy to design the peaks and forget that the valleys are doing real work.

Call the valley what it actually is: a recovery beat. Not the part of the game you get through to reach the good part — the part that makes the good part legible as good.

Red Dead Redemption 2 is close to a pure test case for this, because so much of it is the recovery beat. Looting a body takes a real few seconds of holding a button, not an instant grab. Skinning an animal is its own small animation, not a menu prompt. At camp, running is discouraged — other characters will comment if Arthur sprints past them — and the incidental upkeep (grooming a horse, cleaning a weapon, cooking over a fire) has no urgency to it at all. None of this moves the plot forward. All of it is downtime, mechanically enforced.

The common reading of this — including a piece that got me thinking about this in the first place — is that the slowness serves the story’s themes of reflection and consequence. That’s true, but it’s not the only thing happening. Mechanically, RDR2 is mostly built out of Fullerton’s valleys, with sharp, short peaks (a shootout, a heist, a story beat) rising out of them. The slowness isn’t an absence of design. It’s most of the curve.

Testing it against WoW Forever

The hypothesis held up in the beta — and in one place, better than I’d expected, because it wasn’t even the system I went in looking to test.

The campfire feature is doing exactly what the rested-XP redesign suggests it was built to do. People gather at them and talk — not because the game asks them to, but because it built a reason to stop moving and a shared space to do it in. The campfires I passed had actual conversation happening in and around them, not just characters standing on a buff icon. That’s the recovery beat succeeding on its own terms, as a social space, not just as a number.

The rest splits between two things worth keeping separate, since crediting one system for both would overstate the case. Slower travel and no real pressure to rush toward max level left room to actually take in the new graphics overhaul, and to read quest text for the world it’s describing instead of skipping straight to the objective marker. That’s Fullerton’s mechanism directly: enough slack for detail to register instead of getting steamrolled by the next objective. It’s also squarely a payoff for one kind of player over another, in Bartle’s terms — an Explorer gets rewarded by that slowness, where an Achiever grinding toward max level would likely feel the same pacing as friction instead.

The most interesting data point wasn’t designed at all. Waiting on a contested mob spawn because other players were hunting the same target didn’t feel like downtime a system imposed on me — it felt like being inside a world other people were actually living in, population density standing in for lore. Nobody at Blizzard authored that specific wait; it’s what happens when a leveling zone has real population pressure on it. But it’s still doing Fullerton’s job: a lull that makes the eventual kill feel earned instead of automatic. It’s a different, arguably stronger claim than “the designers nailed the pacing” — it’s evidence the game rewards patience even in the places nobody specifically designed for it.

Conclusion

The claim isn’t that slow games are inherently better designed than fast ones — plenty of padding really is just padding. It’s that deliberate slowness, when a game earns it, isn’t the game failing to keep pace with a faster culture; it’s one of the few places pace is still set by the thing you’re doing, not by everything trying to get faster around it. RDR2 earns it by building almost the whole game out of the valley. WoW Forever, on the evidence of one early session — campfires people actually gather at, world detail people actually stop to notice, contested waits that read as a living world instead of a queue — is earning it too, through a mix of systems built for exactly this and population dynamics nobody had to design at all.

Further reading: