Factitious Game All articles
Features

The Glitch Is the Message: What Speedrunners Are Actually Saying When They Break a Game's Story

Factitious Game
The Glitch Is the Message: What Speedrunners Are Actually Saying When They Break a Game's Story

Picture this: someone sits down to play Celeste — a game about grief, anxiety, and the slow, unglamorous work of climbing a mountain — and finishes it in under thirty minutes. They don't read the journal entries. They clip through a wall in chapter four. They skip the scene where Madeline confronts her darker self.

Is that player disrespecting the story? Or are they doing something stranger and more interesting — using the game's own architecture to ask a question its developers never anticipated?

The speedrunning community has a complicated reputation outside its own circles. To casual observers, runners are the people who treat games like obstacle courses, stripping away everything that isn't forward momentum. But spend any time in the actual community — watching GDQ marathons, reading forum breakdowns of route optimization, listening to runners talk about why they chose the games they did — and a different picture emerges. Speedrunning narrative games isn't a rejection of story. For a lot of runners, it's a form of obsessive engagement with it.

The Archive and the Exploit

There's a useful way to think about what a speedrunner does to a narrative game: they turn it inside out. Where a first-time player experiences a story as something that unfolds to them, a runner experiences it as something they have already internalized so completely that they can navigate its seams.

You can't effectively speedrun a game you don't understand. To find the skip, you have to know what you're skipping — what the intended sequence is, why the developers built the path that way, where the logic of the world is load-bearing and where it's decorative. In that sense, a runner who blows past a cutscene has probably watched that cutscene more times than most players who sat through it dutifully.

This is especially true in games with dense, authored narratives. Runners of Hades, What Remains of Edith Finch, and Disco Elysium aren't skipping the story because it bores them. They're operating from a position of such deep familiarity with the story that they've graduated to a different relationship with the text entirely.

Sequence Breaking as Literary Criticism

Here's a provocative framing: sequence breaking — the technique of accessing areas or triggers out of the intended order — is a form of literary criticism.

When a runner finds a way to reach the final boss before the midgame revelation that was supposed to recontextualize everything, they're implicitly asking: does this story hold up if you already know the twist? When they skip the tutorial that explains the game's central metaphor, they're asking: was that explanation actually necessary, or was the game underestimating us?

Not every exploit yields a meaningful answer. Some skips exist purely because a collision box was miscalculated. But the culture around route discovery — the documentation, the debate, the collaborative refinement — has a genuine intellectual texture to it. Runners argue about whether a particular skip "breaks" a game in the sense of ruining it, or just exposes something the developers left vulnerable. That distinction matters to them.

Content Overload and the Need for a Different Gear

It's worth acknowledging the context we're all living in. The average American with a gaming habit is staring down a backlog that would take years to clear, while new releases, Game Pass additions, and indie darlings accumulate faster than anyone can reasonably absorb them. In that environment, the relationship between player and narrative is under real strain.

Speedrunning offers one response to that strain — not escapism exactly, but a way of being in a relationship with a game's story without being subject to its pacing. There's something almost defiant about it. The story wants to take forty hours. The runner says: I'll give it thirty-seven minutes, and I'll understand it more deeply than most people who gave it the full forty.

That's not a claim every runner would make for themselves. But it's a dynamic worth taking seriously.

The Accidental Philosophy

What's genuinely fascinating about speedrunning culture is how rarely it frames itself in these terms. Most runners aren't walking around calling themselves critics of authored experience. They're optimizing movement tech and shaving seconds off splits and arguing about whether a particular skip is consistent enough to include in a serious run.

But the philosophical implications are there whether they're named or not. Speedrunning implicitly challenges one of the core assumptions of narrative game design: that the developer's intended sequence is the correct one. It says the game exists as a system, not just a story, and that system can be engaged with on different terms than the ones offered at the title screen.

For a medium that's spent decades arguing for its legitimacy as a storytelling form, that's a genuinely interesting provocation. It suggests that games tell stories in ways their authors don't fully control — that the story lives in the architecture as much as in the script.

What Developers Make of It

Some indie studios have started leaning into this. Developers who show up at GDQ to watch their games get dismantled in real time, who patch out certain exploits while quietly leaving others intact, who design hidden sequence breaks as easter eggs for exactly this kind of player — they're acknowledging that the speedrunning community isn't the enemy of their narrative. It's a different audience, asking different questions, and sometimes surfacing things about the work that the creators themselves hadn't noticed.

That's a generous and honest way to think about authorship: not as a fortress to be defended, but as a structure that reveals itself differently depending on how you approach it.

Stories That Play You Back

The tagline on this site is that stories play you back. Speedrunning is a vivid illustration of what that can look like when the player refuses to be passive about it.

A runner who finishes a narrative game in thirty minutes hasn't avoided the story. They've metabolized it, stress-tested it, and returned something back to the community about how it holds up under pressure. That's a form of engagement most developers would be lucky to inspire.

Next time you watch a speedrun of a game you love and feel that instinctive flicker of protectiveness — they're skipping the good parts — sit with it for a second. Ask yourself what the runner might know about those good parts that you don't. The answer might surprise you.

All Articles

Related Articles

Why Rough Edges Hit Harder: The Case for Indie Games as the Last Honest Storytellers

Why Rough Edges Hit Harder: The Case for Indie Games as the Last Honest Storytellers

These Indie Games Are Breaking the Rules of Storytelling to Tell Us the Truth

These Indie Games Are Breaking the Rules of Storytelling to Tell Us the Truth

Too Much Freedom Is Its Own Kind of Cage: The Illusion of Infinite Choice in Narrative Games

Too Much Freedom Is Its Own Kind of Cage: The Illusion of Infinite Choice in Narrative Games