Zero Radius Games All articles
Game Design

Chaos Runners: How Glitchy Indie Games Built Their Own Competitive Scene

Zero Radius Games
Chaos Runners: How Glitchy Indie Games Built Their Own Competitive Scene

Photo: competitive gamer speedrunning indie game glitch screen, via www.shutterstock.com

There's something almost poetic about a game being "finished" by breaking it. Not finished in the sense of credits rolling, but finished in the way a craftsman finishes a table — sanded down, refined, every flaw mapped and catalogued until it becomes something entirely new. That's what the speedrunning underground has been quietly doing to indie games for years now, and in 2024, it's louder than ever.

What started as hobbyists racing through Nintendo classics in their basements has morphed into a sprawling, highly technical subculture. And at the bleeding edge of that scene? Experimental indie games — titles so weird, so rough around the edges, or so deliberately chaotic that runners have turned their very instability into a competitive art form.

The Glitch Is the Game

Ask any serious speedrunner what makes a game "good" for running, and they'll rarely mention polish. What they want is depth — and sometimes the deepest part of a game is the part the developer never intended to ship.

Take Celeste, the beloved indie platformer from Maddy Thorson and Noel Berry. On the surface, it's a tight, emotional platformer about climbing a mountain. Underneath, it's a physics sandbox that runners have cracked wide open. The "extended hyper" and "wave dash" techniques — both unintended byproducts of the game's movement engine — didn't just survive the speedrunning community's scrutiny. They became the whole point. Maddy Thorson has openly discussed embracing these discoveries rather than patching them out, a decision that arguably doubled the game's competitive lifespan.

That philosophy — letting the community own the unintended stuff — is increasingly common among indie developers who understand what their player base actually values.

When the Developer Hands Over the Keys

Some studios go even further, essentially co-developing the speedrun meta alongside their community. Hades by Supergiant Games is a great example. The game launched into Early Access in 2018 and runners were already dissecting it before the full release. Supergiant watched, listened, and deliberately left certain movement interactions intact even when they could have been "fixed." The result? A speedrun scene that's still active years later with a genuinely competitive leaderboard ecosystem on Speedrun.com.

But the more interesting cases — the ones that feel most at home here at Zero Radius — are the smaller, weirder titles. Games that were already experimental in their design, and became something else entirely once runners got hold of them.

Neon White, for instance, was designed with speed in mind. But the community found movement tricks the developers hadn't mapped out, creating a secondary layer of optimization that turned an already fast game into something borderline incomprehensible to watch. Runners aren't just playing the game faster — they're playing a different game, one that exists in the margins of the original.

The People Behind the Times

Spend any time in speedrunning Discord servers or watching Games Done Quick marathons, and you start to notice something: these aren't people casually goofing around. They're methodical, obsessive in the best way, and deeply invested in the games they run — often more invested than the average player who simply completes them.

Runners like TASBot contributors and top-of-leaderboard competitors treat route optimization with the same seriousness a chess player brings to opening theory. They document everything. They share findings openly. And when a new glitch drops — especially in a beloved indie title — the community mobilizes fast.

One runner in a popular Hollow Knight Discord put it simply: "The developers made a game. We made a sport."

That's not disrespect. That's a genuine form of creative inheritance.

Broken by Design vs. Broken by Accident

Here's where things get philosophically interesting. There's a growing subset of indie developers who are intentionally designing games with speedrunning in mind — building in hidden depth, leaving certain systems deliberately underspecified so runners have room to discover things. It's a fascinating inversion of traditional game design logic.

But purists in the speedrunning community sometimes push back on this. There's a difference, they argue, between a game that rewards exploration of its systems and a game that's essentially handing runners a cheat sheet. The magic of classic speedrunning — the reason watching someone clip through a wall in a 1996 platformer still feels electric — is the discovery. The sense that a human being found something the creators missed.

Experimental indie games sit in a sweet spot here. Because they're often built by small teams with limited QA resources, their edges are genuinely rough. The glitches are real. The sequence breaks aren't planted Easter eggs — they're genuine cracks in the foundation that runners have turned into doors.

Why This Matters for Indie Dev Culture

For indie studios watching their games get dismantled by speedrunners, the lesson isn't "ship more bugs." It's something subtler: depth beats polish when it comes to community longevity. A game with interesting, complex systems — even imperfect ones — will attract people who want to live inside it, not just visit.

The speedrunning underground has essentially become a second tier of game criticism. A ruthless, loving, technically obsessive form of engagement that tells developers more about their own games than any review ever could.

At Zero Radius, we've always believed the most interesting games are the ones that push past conventional boundaries. Speedrunning culture proves that sometimes the most radical thing a game can do is simply leave enough room for players to find something the developer never put there.

The edge of the map isn't the end. For runners, it's the starting line.

All Articles

Related Articles

Breaking on Purpose: Why Indie Devs Are Shipping Glitches as Features

Breaking on Purpose: Why Indie Devs Are Shipping Glitches as Features

Less Is More: The Quiet Revolution of Minimalist Indie Game Design

Less Is More: The Quiet Revolution of Minimalist Indie Game Design

The Loudest Silence: Why Some Indie Games Are Defined by What They Leave Out

The Loudest Silence: Why Some Indie Games Are Defined by What They Leave Out