Takedowns — When Fan Projects Get Shut Down
A running collection of fan projects — mods, remakes, recompilations, private servers — that rights holders shut down, and why. The pattern matters more than any single case: the thing that draws fire is rarely the thing modders worry about.
Cross-reference: rest of the miscellaneous section →
../index.md.
The pattern
The common belief is that you are safe if you:
- require a legitimate retail copy,
- ship no original assets or code,
- release for free, or
- avoid leaking anything.
Every one of these has failed in practice. The strongest predictor of a takedown is not how the fan project is built but whether it overlaps a live commercial product — a current release, a planned remaster, a competing online service, or a publisher's own cancelled-then-revived ambitions.
Signals that reliably raise risk:
| Signal | Why it attracts attention |
|---|---|
| Popularity spike | A mod big enough to trend competes for the same attention as the official product. |
| Monetization | Donations, Patreon, shops, sponsor builds — even non-profit-adjacent money changes the legal picture. |
| Online / private servers | Emulated or private multiplayer directly substitutes for a paid service (Blizzard, MMO projects). |
| A remaster or sequel in flight | A fan remake of something the publisher is about to re-sell is competition, not homage. |
| Asset reuse | Ripped art, music, or code gives a clean claim, even when the project runs on a retail copy. |
| Enforcement mood | The same class of project is sometimes greenlit and sometimes axed; there is no consistent rule. |
Two things are worth separating:
- A cease and desist letter — a demand, usually complied with immediately.
- A filed lawsuit / injunction — a court outcome, with a permanent bar and sometimes money. Rare, but real (Turtle WoW).
Cases
| Project | Rights holder | Year | Outcome | Stated / likely trigger |
|---|---|---|---|---|
| H2M | Activision | 2024 | C&D ~1 day before launch; project closed | Popularity competing with a new release |
| The Last of Us 2 multiplayer mod | Sony Interactive Entertainment | 2026 | Requested not to release; scrapped | Overlap with a shelved official online mode |
| Turtle WoW | Blizzard | 2025–26 | Lawsuit; permanent injunction; servers closed | Private server substituting a live service + donations |
| GTA Vice City Nextgen Edition | Take-Two / ESA | 2025 | Channel terminated, then links pulled | Port competing with the Definitive Edition |
| Nintendo fan cases | Nintendo | 2015–2026 | Two C&Ds; one self-cancellation | Asset reuse; announcements of official remakes |
| Retro ROM-hack / fan-remake cases | Square Enix, Sega, Hasbro, Konami | 2009–2014 | C&Ds weeks before or after release | Direct competition; inconsistent enforcement |
Takeaways
- "We don't ship leaked content" is not protection. H2M ran on a retail copy and shipped nothing ripped, and still took a pre-launch C&D.
- Keep fan work in your own words and your own binaries. Not because it is the only thing that draws fire, but because it removes the easy, uncontestable claim and narrows the dispute to competition and trademark.
- Free is not a shield, and monetization is a beacon. Removing money lowers risk; it does not remove it.
- Announced official remakes are a countdown. When a publisher revives something a fan project covers, expect the fan project to be the first casualty — either by letter or by self-cancellation.
- Enforcement is arbitrary. Identical projects are treated differently, so precedent is weak; a polite takedown is the cheapest exit.
Sources are listed on each case page. Facts reflect reporting at the time of writing and are revised as cases develop.