Skip to content
E
Egmatic
Your Game Got Cloned: What to Do About It
game cloned what to doindie game clonesprotect your game from clonesgame cloningindie game copyrightdmca takedown game

Your Game Got Cloned: What to Do About It

When your game gets cloned: archive first, know what copyright protects, file a DMCA notice where it fits, out-ship the copycat where it does not.

Vladislav KovnerovOctober 13, 202617 min

The law protects less of your game than your anger believes and more of it than your despair does. Copyright covers the expression, the art, the audio, the text, the particular code, and it does not cover the idea, the mechanics, or the rules; so the effective response to a clone is rarely a courtroom, and it is never silence. It is a dated trail of artifacts, a takedown notice you can file in an afternoon, and a version of the game only you can keep building.

The threads that pulled this playbook together ran through developer communities in late September. One developer reported that a game called Dear Passengers had already been carbon cloned and released as DLC. Another watched copycats of an unreleased viral hit gather players while the original was still in development. The sharpest line in the pile was a question: what is the point of developing anything if you will be beaten to the punch? Cloning used to be something that happened after launch, to proven games; the current wave arrives during development, and generative tools compress the copy window from months to days. The policy side of that shift, what platforms disclose and what they filter, is covered in our article on AI-generated games and Steam. This one is the operational sequel, written by the team building Egmatic: the clone exists, it is yours, and here is the order of moves.

One honest note before the moves. This is a playbook, not legal advice, and it leans on United States rules because they are the best documented and most storefronts route through them. For a dispute with real money attached, one hour of an intellectual property lawyer costs less than a week spent in the wrong order.

Quick answer

If the clone reuses your files, your code, your name, or your store page text, you have real leverage: every major storefront responds to copyright notices, and Google states its policy in one line: compliance with the Digital Millennium Copyright Act. If the clone copies the idea and the rules while redrawing everything, you mostly do not have a copyright claim, and your levers are speed, evidence, and cadence. In the United States, registration with the Copyright Office is what keeps the courtroom door open, and the window that preserves statutory damages closes three months after first publication.

What was copiedProtected?Realistic first move
Your art, audio, or writingYes, as fixed expressionDMCA notice to the platform
Your code or project filesYes, the expression in the codeDMCA notice; registration strengthens it
Your game's nameNot by copyright; sometimes by trademarkConfusion report, then a trademark path
Your mechanics and rulesNoOut-ship: updates, content, community
Your store page text, near word for wordThe text yes, the layout mostly noTakedown on the text; archive the page first

The U.S. Copyright Office says it in one sentence on its FAQ: copyright does not protect facts, ideas, systems, or methods of operation, although it may protect the way these things are expressed. For games, the translation matters more than the sentence. Your sprites, your level layouts, your dialogue, your soundtrack, your store description: those are expression, and they are protected the moment they are fixed in a file. The loop of your game, the idea of fishing with grenades, the rule that says matching tiles collapse: those are ideas and systems, and no registration will cover them.

Code has its own clarification. Circular 61 of the Copyright Office, which covers registering computer programs, states that the copyright law does not protect the functional aspects of a program, such as its algorithms, formatting, functions, logic, or system design. What it protects in code is the expressive layer, the particular way your source is written, which is why a stolen project file is a case and a rebuilt imitation of your event logic usually is not.

Names sit in a different drawer entirely. Copyright does not protect names and titles at all; the Office routes those toward trademark law. That split decides your first move more than anything else in this article, because a clone wearing your name is a different problem, and often an easier one, than a clone wearing your mechanics.

The canonical case of the lawful clone is not from this decade. Threes shipped in early 2014; within about a month, clones of it existed, and one of them, the open-source 2048, was built as an improvement of two earlier Threes clones, with its own author describing it as conceptually similar. It was lawful, it was free, it carried an MIT license, and it spawned a wave the press compared to the flood of Flappy Bird variants. Nothing in that chain was a copyright case. It was a market event, and the Threes team answered it in public, in writing, with the design history of their own game. That is the template for the second half of this article.

The first hour: archive, classify, hold

Archive before anything else. Screenshot the clone's store page, capsule, description, trailer, publisher name, and any downloadable build, with the URL bar and a visible date. Store pages change once they notice attention, and evidence that disappears with the page is gone for good. Download the build if there is one; a binary is stronger than a screenshot.

Classify what was actually copied. Work through the table above and name it precisely: assets, code, name, page text, or only the shape of the game. The remedies are attached to that column, not to the feeling.

Hold the rage post. A public callout is a real lever, and it cuts twice: it is free advertising for a clone nobody had heard of, and it warns the copier to delete what you have not archived yet. Decide after the archive exists, not before.

Check the platform's policy lanes. Copyright is one lever; most stores also have spam and impersonation rules. After Flappy Bird's removal in 2014, Apple and Google began rejecting games merely for having Flappy in the title, which is a similarity policy rather than a copyright verdict. File both lanes where both fit; they are reviewed by different teams at different speeds.

Evidence that holds up, and the envelope that does not

Start by burying the most common myth. The practice of mailing a copy of your own work to yourself, the poor man's copyright, has its own entry in the Copyright Office FAQ, and the answer there is flat: there is no provision in the copyright law regarding any such type of protection, and it is not a substitute for registration. The envelope proves nothing a court cares about.

What holds up in the United States is registration, for two mechanical reasons. First, section 411 of the copyright statute says that no civil action for infringement of a United States work shall be instituted until registration of the copyright claim has been made; the case cannot even be opened without it. Second, section 412 says statutory damages and attorney's fees are unavailable for infringements that begin before registration, unless the registration is made within three months of first publication. The practical translation for a solo developer: register the build you announce, not the build you eventually sue over. Registration is a filing fee and a deposit copy through the Office's portal; the current fee schedule is published on copyright.gov, and the paperwork is an afternoon.

For disputes that stay small, the Copyright Office also runs the Copyright Claims Board, a small-claims venue built for this scale, with its caps and process described on the Office's site.

Below the legal line, dated artifacts still matter, if you are honest about what they prove. Version control history, exported builds with timestamps, press emails, festival submissions, an itch page that has been public for a year: none of these decide a courtroom by themselves, because self-authored timestamps are trivially forged, and any lawyer will say so. Their real value is triage and credibility. Platforms accept them as context, communities read them as a record of who was building in the open, and they cost nothing if your habits already produce them. The habit itself is worth building, and our guide to version control and backups covers it for no-code projects.

The tier above your own files is third-party dates: the store page that went live on a date the platform logged, the festival listing, the press coverage, the demo that was downloadable while the copier's account did not exist yet. You cannot forge those retroactively, and neither can the clone. That asymmetry is the quiet argument for putting a public coming-soon page up early: it is a timestamp someone else maintains for you.

Filing the takedown: the DMCA afternoon

The Digital Millennium Copyright Act is the reason a solo developer can move a listing without a lawyer. Section 512 of the statute requires online service providers to designate an agent to receive copyright notices, to publish that agent's contact information on their sites, and to register it with the Copyright Office's public Designated Agent Directory. Find the platform's entry in that directory, or its dedicated web form: Google keeps a legal removal flow and states plainly that it complies with DMCA notices, and Apple routes intellectual-property complaints through its legal dispute forms. The notice itself has a statutory shape, and section 512(c)(3) lists what makes it effective:

  • your signature, physical or electronic, as the rights holder or an authorized agent
  • identification of the copyrighted work claimed to have been infringed
  • identification of the material to be removed, with enough information to locate it
  • your contact information
  • a statement of good-faith belief that the use is not authorized
  • a statement, under penalty of perjury, that the information is accurate and you are authorized to act

Two properties of this machine deserve respect. A notice is not a verdict: the accused can send a counter-notice, and unless you file a court action, the platform restores the material within ten to fourteen business days. And the machine bites in both directions: section 512(f) makes anyone who knowingly materially misrepresents infringement liable for the damages, costs, and attorney's fees of the party they accused. A takedown is a cheap instrument; a misrepresentation claim is not. Aim it at copied expression you can point to on the page, never at a mechanics clone you are angry about.

If the archive says the copier redrew everything and kept only the idea, there is no notice to file, and the fight moves entirely to product. This is the oldest lane in indie games, and the team that mapped it is Vlambeer. Their browser game Radical Fishing was copied before they could ship their own expanded version, and Polygon's account of the incident is blunt about the cost: it damaged motivation so badly that the success of Super Crate Box on iOS was what kept the studio from going out of business. Their answer became the template the industry still borrows: finish the better game anyway, and talk about cloning in public, so that press and community carry a reputation cost the law does not. Ridiculous Fishing shipped in 2013 and is the game people remember; the copy survives mainly inside the story about copying.

What out-shipping means for a team of one, in practice:

  • Update cadence the copier cannot match. A clone is a snapshot. A live game that ships content on a rhythm leaves the snapshot behind within weeks, and players notice which of the two is alive.
  • Assets the clone cannot inherit. Player accounts, cloud saves, community threads, a history of devlogs: these compound over time, and none of them can be lifted out and pasted into another game.
  • Visibility you build rather than borrow. The clone competes for the same shelf you do, and the mechanics of that shelf, which surfaces exist and which signals they read, are mapped in our guide to the Steam store algorithm.
  • A name strangers can find. The Wordle wave showed the other edge of names: confusion alone drove more than 200,000 downloads in about a week to an unrelated, years-older app that happened to share the name. If the name is yours and visible, being first becomes legible to strangers.

Prevention that pays before a clone exists

Register the build you announce. The three-month statutory-damages window starts at first publication; registering right after the coming-soon page goes live is the cheapest insurance in this article.

Keep the public trail shorter than the private one. Closed playtest rounds give you signal without exposure, and how to recruit playtesters covers the trusted-tester route. Go wide only when the build can survive imitators; the timing of that widening is its own decision, mapped in when to turn your playtest into a demo.

Separate the demo from the game. A demo that is provably not the full build protects you twice: it limits what a copier can rip from a public artifact, and it limits what a cracker can try to turn into the full game. In the community threads behind this article, one developer's demo had attracted a cracking attempt by its third download; protection matters from the first download, not at scale. How to put a public artifact up in the first place is covered in our guide to hosting a playable web demo.

Export and date everything, continuously. Exported, versioned project files are insurance against more than clones; they are the artifact you can hand a platform, a lawyer, or a journalist, with dates already on them. The export habit also survives the clone scare: it is the same file that recovers your project after a disk failure.

Mind the name before it matters. Search the name against the storefronts and a search engine before you print it on anything. A name you can own beats a name you have to share with an app that shipped five years earlier.

Common mistakes

  • Filing a DMCA notice against a mechanics clone. It fails on the merits, it teaches the platform to discount your next, valid notice, and under section 512(f) it can hand the copier a claim against you.
  • Trusting the envelope. The poor man's copyright has no provision in the law; the Copyright Office says so in those words.
  • Registering only after the clone appears. Registration still opens the courtroom door, but the three-month window for statutory damages usually closed at launch.
  • Posting before archiving. The rage thread tells the copier exactly what to delete.
  • Undercutting the clone on price. A price war against someone who copied your work is a war against your own margins; win on cadence and trust instead.
  • Treating every similar game as a clone. Genre waves are lawful and most lookalikes are parallel evolution. Read the archive before picking the fight, because being wrong loudly carries its own cost.

How Egmatic fits

Egmatic, the no-code 2D editor this blog belongs to, exists because most of this article is post-export work, and post-export work is where solo developers are most tired. Provenance of your own artifacts became a live fear in 2026, and the honest answer to it is mechanical rather than emotional: a project file you can export at any time, version history you can point to, autosave and rollback so the trail is continuous instead of remembered, and a build pipeline that keeps a demo provably distinct from the full game. That ship layer is what we are wiring next to the editor, so that publishing a build and dating it stop being two separate habits. The AI inside the editor plays the role we believe it should play in a cloning story, a craft amplifier under your direction rather than a substitute for your authorship: you direct, it executes, and every file stays yours. We will state the stage plainly, the way this article states the law: Egmatic is pre-alpha, we announce no dates we cannot keep, and the waitlist at egmatic.com is where you can reply with the provenance artifact you would want wired first, because requests that arrive during pre-alpha are the ones that steer the build.

Artifacts that prove themselves.

Egmatic is a no-code 2D editor and engine with a ship layer under construction, built so dated exports, versioned project files and separated demo builds are the floor, not a habit you have to remember. Reply on the waitlist with the provenance artifact you would want first: requests sent during pre-alpha are the ones that steer the build.

No spam. Unsubscribe anytime.

Conclusion

The order of the playbook is the point. Archive first, because evidence is the only thing that decays. Classify second, because the remedy hangs on what was copied, not on how it felt. Register the announced build, because the law's windows close quietly. File the notice where expression was taken, and out-ship where it was not. The question that opened this article, what is the point of developing anything if you will be beaten to the punch, answers itself in the artifacts: beaten to the punch is a claim about dates, and dates are the one thing a copier cannot retroactively own. The Vlambeer file ends with the studio's best game shipping after the copy had done its damage. The Threes file ends with a design letter the whole industry read. The Wordle file ends with the original game bought by a newspaper for a low seven-figure sum. None of those endings belonged to a courtroom; they belonged to developers who kept building in public, with timestamps they did not have to invent.

Sources