Indie Devs Are Hiding Their Games—And That Chokes Off Discovery
AI-powered cloning is forcing indie game developers into silence. The genre's decade-long demo-driven discovery pipeline is breaking—and no one has a defense that isn't just 'make it too complex to copy.'
The Silence Is the Product
Indie game developers used to solve a fundamental distribution problem with a simple trick: show your game early, build an audience, then monetize. The demo-driven pipeline—show a prototype on Twitter, let it circulate, watch Steam wishlists compound—was the engine that carried Hades, Dead Cells, Hollow Knight, and hundreds of smaller hits to market without big-budget marketing.
That engine is sputtering. Not because demand has dried up. Because a new class of automated cloning is turning the demo pipeline into a liability.
The core binding is brutally simple, as McPixel’s Sos Sosowski put it on social media: “Don’t share your game—no sales. Share your game—gets stolen. How do you even survive as an indie in the current landscape?”
This isn’t a hypothetical anxiety. It’s a capture-the-flag problem that has no defense except silence—and silence is exactly what kills indie discovery.
What’s Actually Being Cloned
The mechanism is straightforward enough that you don’t need insider knowledge to see why it works. An indie dev posts a video of a novel game mechanic—a rotational Tetris variant, a physics-based puzzle system, a movement trick that feels fresh. Within hours, AI-powered pipelines can produce a functional clone: same core loop, different skin, distributed across storefronts and social channels before the original has accumulated enough momentum to matter.
Holmér, whose rotational Tetris prototype was one of the earliest visible victims, described the initial wave to 404 Media this summer. “In the very beginning, just every week, there was a new AI clone,” he said. “I was like, OK, well fuck me, I guess.”
The clones weren’t just superficial copies. They were functional—playable, distributable, and designed to siphon attention from the original during its critical launch window. As Holmér noted, engagement dropped sharply during that first month. The algorithmic ecosystem rewarded speed over substance, and the originals got buried.
But here’s what’s subtler and more important: Holmér eventually found himself “more in the clear” once the wave passed. The clone market saturated, the novelty faded, and he could return to building something he was proud of rather than racing to ship. The question is whether other developers have that luxury—or whether the fear of cloning has already pushed enough people out of the public pipeline that the genre’s discovery engine is permanently degraded.
The Philosophy Behind the Clones
Charlie Greenman, who posted one of those AI-powered clones earlier this year, told 404 Media he saw nothing wrong with what he did. His argument was structural rather than moral: if a concept can be expressed mechanically, is one game copying another? He drew parallels to board games—Blox, Jenga—asking whether their creator owed anything to Tetris. “Whoever created Blox, Jenga, is that a copy of Tetris?”
The analogy is clever but flawed. Board games evolved through decades of cultural osmosis and physical constraint. AI cloning operates at digital speed with zero creative investment. The comparison collapses under its own weight: Jenga didn’t appear overnight because someone fed a Tetris video into a pipeline. It appeared because people built it, played it, and iterated on it.
Greenman’s position also reveals something deeper about the clone economy: the classifiers aren’t just copying games. They’re copying the attention around games. A prototype video generates organic interest—comments, shares, wishlists. The clone captures that interest by appearing in the same feed, with the same visual language, siphoning engagement before the original can convert it into sales. The theft isn’t in the code. It’s in the timing.
The “Soul” Argument—And Why It Doesn’t Help
Some developers have pushed back with what amounts to a Darwinian defense: if AI can copy your game overnight, it wasn’t a real game. It was just a quick cash grab built on a single mechanic, with no soul or vision.
Ivan Lago of Howltide Games articulated this view on social media. “AI isn’t cloning actual games,” he wrote. “It’s just making cheap knockoffs of stuff that was already an asset flip to begin with.”
The argument is intuitively satisfying but strategically hollow. It assumes that the games most vulnerable to cloning are inherently shallow—that only weak ideas get copied, and strong ones survive. But history suggests the opposite: the mechanics most likely to be cloned are often the simplest, most elegant ones. Tetris itself was copied endlessly. Pac-Man spawned thousands of clones. The beauty of a good mechanic is that it’s easy to recognize and easy to replicate.
More importantly, the “soul” argument doesn’t solve the discovery problem. Even if a clone lacks the original’s polish, narrative depth, or artistic vision, it still siphons attention during the critical launch window. The original developer still loses sales, still loses momentum, still loses the algorithmic boost that comes from early community engagement. The clone doesn’t need to be better. It just needs to be first in the feed.
The Pipeline Is Breaking
The real damage isn’t to individual games. It’s to the infrastructure that delivers games to players. The indie discovery pipeline—prototype demos, viral moments, wishlist compounding—has been the genre’s lifeblood for a decade. It allowed small teams with big ideas to bypass traditional marketing and reach audiences directly. It rewarded risk-taking, novelty, and speed.
That pipeline depends on one condition: developers must be willing to show their work publicly before it’s finished. If they hide their prototypes to avoid cloning, the pipeline starves. No demos means no buzz. No buzz means no wishlists. No wishlists means no sales. The ecosystem collapses from the top down.
Holmér’s experience illustrates the paradox. He eventually found creative freedom once the clone wave passed—but only because he could afford to wait. Most indie developers can’t. They’re racing against cash flow, against burn rates, against the need to prove their concept to publishers and players simultaneously. For them, silence isn’t a luxury. It’s a death sentence.
What Happens Next
There’s no clean solution. Legal frameworks haven’t caught up to automated cloning—copyright protects expression, not mechanics, and the line between inspiration and appropriation is blurry when AI can generate infinite variants overnight. Platform policies are reactive at best. Community norms are fraying.
The most likely outcome isn’t a return to the old pipeline. It’s a bifurcation: large studios with legal teams and resources will continue to release demos publicly, protected by brand recognition and litigation threats. Small indies will retreat into private development, sharing work only after launch or through closed beta networks. The discovery engine will slow, and with it, the genre’s diversity.
Holmér’s closing observation is both accurate and bleak. “There’s way less engagement now,” he said. “I feel more in the clear to take my time to actually make something right, something good I can be proud of, and not just get it out there as soon as possible.”
That’s the wrong outcome for the genre. A world where indies build in private, ship polished products, and hope for organic discovery is a world with fewer risks taken, fewer novelty mechanics tested, and fewer voices in the pipeline. The clones aren’t just stealing games. They’re stealing the uncertainty that makes indie development worth the gamble.
The question isn’t whether AI can copy a game. It’s whether the ecosystem can survive a decade in which the cost of showing your work outweighs the benefit.