indiegame

🧵 Anatomy of a viral hit | A cloner angrily denounces someone for cloning him

1/ First, the timeline: This X post went up on October 17, and Kotaku reported on it on October 18. NoGlyph’s game, *Needle In A Haystack*, launched on Steam on September 29—but it was itself a clone of *Needle In A Haystack Simulator*, which went viral in August.

On October 17, NoGlyph posted on Steam, accusing another clone, *A Game About Needle In A Haystack*, of copying their code: 13 classes with identical names, 39 identically named methods that were byte-for-byte the same, and even error messages copied verbatim—including one pointing to a shader in their own project.

Lead programmer Jahvin offered a diagnosis on Discord: this was a textbook case of Claude-assisted decompilation—decompile a closed-source game to extract its source code, then have Claude paste it into your own game.

2/ The first layer of what made this blow up is the irony: a cloner gets cloned, then angrily denounces cloning. Steam players had just one word for it: “karma.” Irony is the best fuel for virality; the story tells itself.

3/ The second layer is a real trend. One Kotaku article tied together three things: a Roblox creator cloned the unreleased *Escape the Walls* in just 24 hours using nothing but a video on X, saying, “Claude did everything for me; I just sat in my chair and watched”; Alliance Arts canceled plans for a demo of *Drunken Goddess Reflux* outright, fearing it would be copied by AI; and Kotaku’s conclusion was that there will be fewer demos, fewer early access releases, and fewer trailers in the future.

4/ The formula: dramatic irony (a cloner fighting for their rights) + validation from a real trend (AI cloning is already an industry reality) + a sweeping industry-level conclusion (we won’t see demos anymore).

Every trailer you release now is free material for AI cloners. In the future, will you release the game first—or the trailer? #VibeCoding #IndieGame