You Can't Break What Won't Stay Still: The Indie Devs Fighting Back Against Speedrunners

There's a certain kind of gamer who, upon finishing a great game, immediately asks: how fast can I do that again? Speedrunning is a beautiful subculture — a blend of obsessive memorization, pixel-perfect execution, and genuine community love for the games being dissected. We've celebrated it here at Tiny Windows Games before, and we mean it. But something interesting is happening on the other side of that relationship. A growing pocket of indie developers is pushing back — not with hostility, but with design.

They're building games that simply refuse to be solved.

The Optimization Problem

Here's the thing about speedrunning: at its core, it's about eliminating uncertainty. The runner studies a game until it becomes a known quantity — every enemy spawn, every frame window, every shortcut. The goal is to compress chaos into a repeatable script. And for a lot of games, especially tightly designed platformers or linear action titles, that's entirely possible. Beautiful, even.

But some developers look at that process and see something they don't want to invite. Not because they hate speedrunners — most of them are fans — but because their games are built around a feeling that only survives uncertainty. The moment a player can reduce their experience to a checklist, that feeling evaporates.

"I want people to still be surprised on their twentieth run," says one developer of a small roguelite dungeon crawler that's earned a quiet cult following on itch.io. "If someone can pull up a route and follow it blindfolded, I've failed at what I was trying to make."

Randomization as a Design Philosophy

The most obvious tool in this anti-optimization toolkit is procedural generation — levels, loot, enemy placement, even narrative beats that shuffle on every playthrough. Games like Spelunky and The Binding of Isaac popularized this approach years ago, and the indie scene has been riffing on it ever since. But the newer wave of developers is getting more deliberate about why they're using randomization, not just that they're using it.

It's the difference between randomization as a content multiplier and randomization as a philosophical statement. One says "we didn't have time to build more levels." The other says "we don't want you to know what comes next, ever."

Some studios are going further, baking unpredictability directly into core mechanics. Timers that drift. Enemy AI with weighted randomness that prevents any single behavior from becoming dominant. Loot tables that actively track what a player has seen before and push rarer outcomes to the surface — not to be generous, but to keep things strange.

Anti-Pattern Mechanics: The Subtler Weapon

Randomization is the loud version of this design philosophy. The quieter version is what some developers call anti-pattern design — building systems that actively punish repetition.

Imagine a puzzle game where the "correct" solution changes based on how many times you've attempted it. Or a combat system where enemies adapt to the player's most-used moves over the course of a session, forcing genuine flexibility rather than optimized button sequences. These aren't glitches. They're features — deliberately engineered friction against the kind of muscle memory that makes speedrunning possible.

One developer working on a small narrative adventure described it this way: "Speedrunners are incredibly smart people. If there's a pattern, they will find it. So my job is to make sure there isn't one — or at least, not one that survives more than a few runs intact."

This creates a fascinating creative tension. Players want to feel skilled. Developers want to preserve surprise. Threading that needle without making the game feel arbitrary or unfair is genuinely hard work.

When Chaos Feels Like Cheating

Not everyone in the community is cheering this movement on. And honestly, that's fair.

There's a real criticism here: randomization can mask bad design. If an encounter is brutal, is it because it's well-crafted, or because the RNG happened to stack every bad outcome at once? Players who put in serious time with a game deserve to feel like their knowledge and skill matter. Pure randomness doesn't reward mastery — it just rewards persistence.

The best anti-optimization games walk a careful line. They use unpredictability to keep things fresh, but they still reward players who understand underlying systems. Knowing how the randomness works — even if you can't predict specific outcomes — is itself a form of mastery. The player who understands the dungeon's generation logic will still outperform the one who doesn't, even if neither can guarantee a perfect run.

That distinction matters. It's the difference between a game that feels alive and one that just feels broken.

The Speedrunning Community's Response

Here's the twist: speedrunners often don't mind. In fact, some of the most passionate communities have formed around exactly these kinds of games.

When a game can't be fully solved, the leaderboard becomes less about a definitive world record and more about variance management — who made the best decisions with the hand they were dealt. That's a different kind of competition, but it's still deeply compelling. Some runners describe it as closer to poker than to a footrace: skill matters enormously, but you're always playing with a shuffled deck.

Games designed to resist optimization sometimes end up with more active speedrunning communities than their more predictable counterparts, precisely because the category never gets "stale." There's always another run worth watching.

Small Games, Big Questions

What makes this conversation feel particularly alive right now is the scale at which it's happening. These aren't big-budget studios experimenting with AI-driven adaptive systems. These are solo developers and two-person teams, building in GameMaker and Godot, releasing on itch.io and Steam with $5 price tags and hand-drawn pixel art. They're asking genuinely sophisticated design questions with genuinely tiny resources.

And they're landing on answers that the larger industry hasn't fully grappled with. What does replayability actually mean? Is a game more valuable because it can be mastered, or because it can't? What do we owe players who want to break our games — and what do we owe ourselves as designers?

There's no clean answer. But the fact that indie developers in spare bedrooms across the country are wrestling with these questions — and building real, playable experiments to test their theories — feels like exactly the kind of thing this scene is for.

Small windows. Big ideas. And a game that looks a little different every time you open it.