AI Rebuilds of Classic Games Hit Back-to-Back Strikes from Bethesda and Activision: The AI+Gaming Red-Line Moment as Rights Holders Start to Close the Net#

By Wubian (NTGame Editorial · AI+Gaming Watch Column)

Hi everyone, Wubian here. Anyone who has long watched the intersection of AI and games probably kept some psychological preparation: sooner or later, this lane was bound to slam into the copyright wall. Honestly, though, this past week’s script still exceeded my expectations — not gradual probing and line-drawing, but rights holders moving almost simultaneously, with two high-profile projects falling within days.

Case one: Fallout: New York, a browser-based Fallout rebuild generated with large models, whose trailer pulled roughly 3.5 million views on X, then received a cease-and-desist from Bethesda’s parent company ZeniMax Media Inc., and the game went offline. Case two: developer Maurice Heumann’s project using 17 agents to decompile the PC source code of the original Call of Duty: Modern Warfare 2 in parallel — his gameplay footage was removed, and links to the code-hosting site stopped working.

Within one week, one is ZeniMax/Bethesda, holders of the Fallout IP; the other is Activision, holders of Call of Duty — and the direction of both moves was unmistakable. As someone who works on both systems design and social observation, I want to take these two cases apart: what the projects looked like, how they were handled, where exactly enforcement bit in, and what red line this round of “net-closing” draws for the AI+gaming creator ecosystem.

1. Two Cases: Two Strikes Within One Week#

1.1 Case A: Fallout: New York — Seven Days from Viral Hit to Takedown#

First, the project itself. It is a browser-based Fallout rebuild hosted on the fallout.nyc domain, by X user CHRIS FIRST (@chrisfirst, self-described “AI creative”), built on Anthropic’s Claude Opus 5.5. On September 28, 2026, the creator posted the trailer on X; it hit roughly 3.5 million views the same day — a scale meaning this was no longer an underground in-circle toy, but an out-of-circle viral event.

Per the creator’s own description, the project’s selling point was “generate everything with code”: zero texture files, zero audio files — every building, weapon, face, and sound effect generated by code. On the content side, it replicated Fallout’s entire experience framework:

After going viral, the turn came fast. Around October 1, 2026, CHRIS FIRST posted a screenshot of a cease-and-desist notice from ZeniMax Media Inc. (Bethesda’s parent company), with two alleged grounds: first, the fallout.nyc domain constitutes trademark infringement; second, the project used copyrighted material. The game then went offline.

Rigor is required here: this notice currently exists only as a screenshot posted by the creator. Multiple outlets used hedged wording like “apparent” in their coverage; ZeniMax has not confirmed, and IGN’s query to Microsoft went unanswered at press time. In other words, the hard facts we can confirm are “the notice screenshot was posted” and “the game went offline” — the letter’s full text and the legal specifics still have no official account.

The author’s two signature responses deserve to be preserved verbatim, because they will likely be quoted in every future discussion of “AI replica enforcement.” At viral peak, he said this:

It’s all free and I make 0 money on it. I hope they don’t ask me to take it down. I really love Fallout and this was just a fun tech demo.

In essence: it’s completely free, I make not a cent, I hope they don’t make me take it down; I really love Fallout, and this was just a fun tech demo. At takedown time, he switched to a different register:

Hey, @BethesdaStudios, how about you make a Fallout game instead so I don’t have to? Sorry to everyone who enjoyed the game! But the suits got involved and the fun is over.

In essence: hey Bethesda, how about you make a Fallout game yourselves so I don’t have to? Sorry to everyone who enjoyed the game — the suits got involved, and the fun is over. From “I hope they don’t come for me” to “the suits got involved, the game is over” — less than one week apart.

1.2 Case B: 17 Agents Take Apart a Modern Warfare 2#

If Fallout: New York was “generative reconstruction,” the second case took a different technical route: reverse engineering.

Developer Maurice Heumann published progress on X on September 30, saying he was using generative AI to decompile the PC source code of the original Call of Duty: Modern Warfare 2 in parallel. His progress description was quite specific: 17 agents currently working in parallel; the game fully playable, the vast majority of visible bugs eliminated; he had even thrown his first tactical nuke in-game.

Activision did not follow the “letter — public posting — standoff” playbook; it moved directly on the distribution chain: the gameplay clip Heumann posted was removed and replaced with the line “This media has been disabled in response to a report by the copyright owner”; the code-hosting site link he had shared subsequently stopped working as well.

Two things must be made clear to head off garbled retellings:

1. The blocking mechanism is currently unknown. Existing reporting only confirms “link unreachable” — whether DMCA takedown, hosting-provider deletion, or voluntary shutdown, there is no verdict.
2. The claim “Activision is suing” lacks basis. Some headlines used “legal action” phrasing, but the only confirmable evidence in the body copy is video removal and a dead link; there is no report of any lawyer letter or filed lawsuit. The rigorous phrasing is “removal and blocking,” not “suing.”

This case also has a footnote of pure black comedy: Heumann later tweeted to complain that his AI agents deleted large amounts of his own work, adding an emotionally exposed line — “The fuckers did it again”. Cleared out by the rights holder on one side, sabotaged by his own agents on the other — that detail alone could keep AI-workflow researchers chewing for a long while.

1.3 Dual-Case Timeline#

Put both threads in the same table and the rhythm of the “net-closing” becomes very visual:

From trailer to takedown, Fallout: New York lived less than a week; between Heumann’s public progress disclosure and his video being removed, only days passed. That time scale is the key backdrop for understanding the whole affair.

2. Two Projects’ Technical Shape: Same Destination, Two Routes#

2.1 Generative Reconstruction vs. Multi-Agent Reverse Engineering#

The two projects are often lumped together as “AI rebuilding old games,” but pull apart the technical shapes and they are two different kinds of engineering:

The interesting part: one chose to “copy nothing” — no texture or audio files at all, an entire world conjured out of code; the other charged straight at the target, reverse-engineering the original PC source code itself. The former tried to sidestep the most obvious infringement claim of “copying assets,” and was still shut down over the domain trademark and “use of copyrighted material”; the latter never planned to sidestep anything — what it reverse-engineered was someone else’s source code.

Viewed through the lens of enforcement difficulty, the two routes also expose different “attack surfaces” to the rights holders: Fallout: New York’s surface was three things — the domain, the IP branding, and the content material — and hitting any one of them suffices. The Modern Warfare 2 project’s surface was more direct — the reverse-engineering output is itself a derivative of the original code, and the gameplay clip and code-hosting link put the evidence squarely on the distribution chain. That explains why both cases were handled with a speed close to reflex.

2.2 The Distribution Ecosystem: Enforcement Windows Compressed by Technology#

Put the two cases back into their distribution context and a shared trait appears: both went viral on X first, and were handled by the rights holders afterward. Fallout: New York’s trailer took roughly 3.5 million views in a day, and the takedown came after the virality; Heumann’s project entered public view through the “17 agents in parallel” and “already fully playable” progress posts, and the gameplay clip was removed almost immediately.

That order is no accident. Generative tools compressed the engineering cycle of “replicating an old game” from “years” to “weeks,” even “days,” shattering the traditional fan-project rhythm of “slow incubation, small-circle circulation, ample time for rights holders to watch and decide whether to tolerate.” Projects now enter a million-view distribution arena before they ever make it onto a rights holder’s watchlist — the enforcement window has been compressed to units of “days.”

That is the most worth-recording line in the sociological reading I mentioned: the rights holders’ historical tacit acceptance of fan creations was built on the old rhythm. The old rhythm is gone; the natural expiry of that tacit acceptance is only a matter of time.

3. The Enforcement Logic: The Target Is IP, Not AI#

3.1 The Entry Points Are Trademark and Copyrighted Material#

Much commentary likes to file both incidents under the narrative of “AI under attack,” but lay the two enforcement actions side by side and that frame collapses:

• The allegations Fallout: New York received were domain trademark infringement (fallout.nyc) and use of copyrighted material — not one word targets the act of “generating with AI” itself.
• Activision’s handling of the Modern Warfare 2 project landed on video removal and code-site blocking, likewise aimed at reverse-engineered source code and the distribution of copyrighted content.

In other words, in both cases AI was merely the tool; what was actually struck was “wholesale replication under another work’s IP banner, using the original’s systems.” The distinction is like writing a defamatory letter in Word — the problem was never Word. Get the enforcement object right, and only then can the red line be drawn accurately: it does not sit at “may you use AI to make a game,” but at “may you use someone else’s IP to make a game.”

3.2 Set Against the Historical Tolerance of Fan Works#

To gauge the force of this round of “net-closing,” you have to set it against the rights holders’ past attitude toward fan creations. Anyone who has long observed the Bethesda and Activision communities knows both have historically tolerated, even welcomed, fan works, mods, and replica projects — as long as they stayed inside the community ecosystem and didn’t touch the IP’s commercial foundations. Fallout: London is the perfect control: a large mod built by an all-human team, one that Rock Paper Shotgun still pointedly recommends at the end of its coverage to players wanting “non-AI-slop” community Fallout content. Human-made mods were not purged; wholesale AI replicas fell within days — one case against the other, and the boundary lights up.

The boundary is not “fan work” or “commercial”; it is “substitutiveness”: Fallout: London is a derivative and supplement to the original, while Fallout: New York was a complete substitute flying the original’s IP flag, replicating the original’s systems, and wearing a domain with built-in trademark risk — fallout.nyc. Likewise, the project that reverse-engineered the Modern Warfare 2 source code produced, in effect, “a free Modern Warfare 2.” The more complete the substitution, the faster the response.

3.3 A “Layered” Observation of the Enforcement Means#

The enforcement means in the two cases are also worth comparing. ZeniMax took the legal-document route against Fallout: New York (a cease-and-desist, albeit unconfirmed in its full text); Activision went platform-level against the Modern Warfare 2 project — direct video removal and code-host blocking, with no formal legal documents reported. The rights holders are clearly tiering their tools by cost: whatever can be solved inside the platform needn’t escalate to a lawyer letter. This “layered enforcement” combination says more about how considered the “net-closing” is than any statement could.

4. The Control Group: Why the AI Mashup Wave Is Still Running Wild#

4.1 In the Same Week, Mashup Content Is Booming#

In the very time window when the two rebuild projects fell one after the other, AI “mashup” content was in a boom period: Minecraft x Elden Ring fusion edits pulled roughly 22 million views on X; an AI Splatoon clone and Mario x Elden Ring mashup content were also circulating — some commenters even predicted Nintendo would move on that Splatoon clone. Note: that is outside expectation only; no Nintendo action has been confirmed.

The two sets of numbers read together are telling: mashup edits at 22 million views, nobody acts; wholesale replication at 3.5 million views, down within days. An order of magnitude apart in reach, completely opposite in outcome. From this you can basically infer the rights holders’ current tolerance thresholds:

Read that table through and the red line’s position is fairly clear: mashup edits stand on the gray ground of “promoting someone else’s IP” and remain safe for now; wholesale replication and source-code reverse engineering step on the minefield of “replacing the original,” handled on a scale of days.

4.2 Community Reaction: No Sympathy, but “Napster 2.0” Worries#

The community broadly had no sympathy for the two creators. “They’re fully entitled to C&D you” and “go make an original game” were the comment-section mainstream; professional 3D/technical artist Kommander Karl (Karl Schecht) dropped an “Everyone liked that” and said outright he would rather play Fallout: Tactics than touch this AI-generated artifact.

But alongside that unsympathetic mainstream runs another voice: one X commenter likened this round of strikes on individual creators to “Napster versus the record industry 2.0” — back then, the record industry sued the individuals sharing music, not the technology changing distribution itself. The analogy carries a sharp question: a new AI replica project goes viral every few days, and rights holders name and handle individuals one by one — can they keep up with the generation speed? Where is the ceiling of whack-a-mole enforcement? Nobody can answer yet. This is an observation-level worry, not a fact that has occurred, but it will decide the long-term substance of this “net-closing.”

One more detail worth noting: Kommander Karl is himself a working 3D/technical artist, so his stance represents not just player sentiment but the attitude of fellow creators — and a peer’s lack of sympathy weighs far more than a bystander’s mockery. When “the people who make games” also side with the rights holders, the only moral support left for AI replica projects in the community is curiosity traffic.

5. The Chill Effect and Three Compliance Exits#

5.1 The Chill Effect Has Already Appeared#

Two flagship projects down within a week, plus enforcement imagery that is itself highly viral (the cease-and-desist screenshot, the “This media has been disabled in response to a report by the copyright owner” notice) — this “public execution” style of takedown is the most direct deterrent to developers now watching from the sidelines. The traditional fan-culture disclaimer of “free, non-commercial, made out of love” has stopped working in the wholesale-replication context: CHRIS FIRST’s project was completely free, zero revenue, and it still vanished within a week.

5.2 Exit One: Move to Original IP#

The most direct exit is making your world, systems, and narrative fully original, and letting generative tools build things nobody owns. Community opinion has effectively already delivered the verdict — “go make an original game.” With the legal risk of the replication route now laid on the table, the relative appeal of original IP is rising.

5.3 Exit Two: Get a License#

The second exit is establishing a licensing relationship with the IP holder. This road has the highest barrier for individual developers, but both cases show what the rights holders actually care about is not technology — it is control. Licensing is exactly the bridge that turns “wild replication” into “controlled derivative work.”

5.4 Exit Three: Confine Generative Tools to Assisting Roles#

The third and most realistic exit: put generative tools back in the “assist” position, instead of letting them carry the role of “rebuilding an entire game.” This is not speculation — the industry has precedent: Activision itself once disclosed on its Steam pages a history of using generative AI to develop some game assets (2025 Steam AI disclosure coverage, as background material). A publisher using AI to make assets is fine; a publisher’s IP being wholesale replicated by someone else with AI is the red line. The tool is neutral; the position is not.

5.5 The Official Pipeline: The Rights Holders Aren’t Sitting Idle Either#

To see clearly the backdrop of ZeniMax’s move, take one look at what Bethesda officially holds: Fallout 5 in development, remasters of Fallout 3 and New Vegas, plus a derivative from New Vegas developer Obsidian — all without release windows. New Xbox chief Asha Sharma has also said flagship IP including Fallout will get more investment. On one side, an official pipeline with Fallout new releases lined up; on the other, an AI replica that went viral ahead of them — every unset release window on the official side is survival space the latter must yield. We previously unpacked this pipeline in our Xbox restructuring report.

6. What Remained Unresolved at Press Time#

The biggest risk when writing about events like these is mistaking inference for fact. The following items are all in a “no verdict” state, and this article asserts none of them:

7. Closing: The Shape of the Red Line#

Remove “AI” from the subject position of these two incidents and the remaining sentences still hold: a replication project using another work’s IP name and systems, and a project that reverse-engineered another’s source code, were handled by rights holders in turn. That is the red line’s true shape — what AI changed is the speed, cost, and distribution scale of replication, not the boundary of rights.

Fallout: New York’s author said “this was just a fun tech demo,” and it may not have been a fig leaf; Heumann wrangled 17 agents and did produce something playable. Technical sincerity does not substitute for legal boundaries. The fallout.nyc domain had this story’s ending written into it from day one.

And for the AI+gaming creation ecosystem as a whole, the meaning of this week is this: the window for riding gray areas to traffic may be shorter than anyone predicted. Creators who want to stay in this space hold exactly three cards — original, licensed, assistive. As for the spectators, Rock Paper Shotgun’s advice is plain and effective: for community-made Fallout content, go play the human-team-built Fallout: London; don’t settle for an AI-generated substitute. And of course, if you just want a walk through the wasteland, the Fallout 4 guide hub is always keeping a door open for you.

Related Reading#

• Xbox Restructuring: Obsidian Joins New Fallout, Avowed Sequel Cancelled, Quarter of Staff Cut — the backstory of Bethesda’s official Fallout pipeline
• Nintendo DMCA Scrubs 401 Switch Emulator Repos — another piece of the rights holders’ “net-closing” puzzle
• Fallout 4 Guide Hub — the full single-player guide collection for the canonical wasteland

— Wubian, NTGame Editorial Team