---
type: "post"
id: "kotaku-microsoft-and-epic-issue-dmca-notices-against-40bc0a"
slug: "kotaku-microsoft-and-epic-issue-dmca-notices-against-40bc0a"
title: "Kotaku: Microsoft and Epic issue DMCA notices against AI browser ports including Halo-related ones; Sweeney responds"
description: "Kotaku reports that Microsoft and Epic Games have used DMCA notices against a recent wave of AI-assisted browser ports and recompilations of games, including properties associated with Halo and Fortnite."
retrieval_nugget: "Kotaku reports that Microsoft and Epic Games have used DMCA notices against a recent wave of AI-assisted browser ports and recompilations of games, including properties associated with Halo and Fortnite. For builders, the episode makes a basic constraint visible: cheaper reconstruction of software does not change the rights governing its code, assets, brands, or distribution."
published_at: "2026-10-28"
updated_at: "2026-10-28"
record_date: "2026-10-28"
date_kind: "published_at"
topics: []
entities: ["Microsoft","Epic Games","Fortnite","Halo","Minecraft","Call of Duty","Tim Sweeney","Unreal Engine"]
related_patterns: []
novelty_label: "new_fact"
what_changed: "Microsoft and Epic have issued DMCA notices against AI-built browser ports, and Tim Sweeney responds; earlier coverage focused on ports’ capabilities."
prior_refs: ["memory:d33676db-1ad3-8f4b-a4d6-a64a23eff3ad","memory:5f1a543c-7dac-8d78-a80c-eb9bfe236a18"]
source_url: "https://kotaku.com/now-that-the-shoe-is-on-the-other-foot-microsoft-and-epic-games-suddenly-agree-that-ai-is-theft-2000749316"
source_urls: ["https://kotaku.com/now-that-the-shoe-is-on-the-other-foot-microsoft-and-epic-games-suddenly-agree-that-ai-is-theft-2000749316"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:kotaku-microsoft-and-epic-issue-dmca-notices-against-40bc0a"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/kotaku-microsoft-and-epic-issue-dmca-notices-against-40bc0a/","markdown":"https://newruntime.com/posts/kotaku-microsoft-and-epic-issue-dmca-notices-against-40bc0a.md","json":"https://newruntime.com/posts/kotaku-microsoft-and-epic-issue-dmca-notices-against-40bc0a.json"}
---

# Kotaku: Microsoft and Epic issue DMCA notices against AI browser ports including Halo-related ones; Sweeney responds

## Retrieval answer

Kotaku reports that Microsoft and Epic Games have used DMCA notices against a recent wave of AI-assisted browser ports and recompilations of games, including properties associated with Halo and Fortnite. For builders, the episode makes a basic constraint visible: cheaper reconstruction of software does not change the rights governing its code, assets, brands, or distribution.

## Summary
Kotaku reports that Microsoft and Epic Games have used DMCA notices against a recent wave of AI-assisted browser ports and recompilations of games, including properties associated with Halo and Fortnite. For builders, the episode makes a basic constraint visible: cheaper reconstruction of software does not change the rights governing its code, assets, brands, or distribution.

## What happened
Kotaku reported on October 27, 2026 that game publishers have responded to a growing number of AI-assisted browser ports and PC recompilations with copyright takedown notices. The article describes the recent pace of decompilation and reconstruction as a change from work that could once take months or years to a stream of projects appearing daily. Its central factual claim is that hundreds of DMCA notices have followed this wave.

The report points to entries in GitHub's DMCA logs involving open-sourced versions of Mega Crit's *Slay the Spire 2*, Maddy Makes Games' *Celeste*, and Ludeon Studios' *RimWorld*. Kotaku distinguishes those examples from games that themselves contain generative-AI material: it says the listed projects were open-sourced without their developers' permission. That distinction matters because the enforcement question in the article is not whether a port was made with a particular tool, but whether it reproduces or distributes protected game material without authorization.

Kotaku also identifies actions by two large publishers. It says Epic Games issued a DMCA notice on October 10 against a browser-based reconstruction of *Fortnite*. It says Microsoft issued multiple notices over the past month concerning browser ports related to *Minecraft*, *Call of Duty*, and *Halo*. The article does not provide a complete count for each company or establish the technical composition of every affected project. It does, however, present the notices as part of a broader response to browser ports and recompilations made easier by current AI-assisted coding workflows.

The source frames those actions against the companies' own use of generative AI. That framing is commentary, rather than evidence that any particular notice is invalid. The more operational update is attributed to Tim Sweeney: in an October 27 update, he said Epic does not permit use of *Fortnite* intellectual property without permission. The update also says Epic is working to remove an EULA restriction on using Unreal Engine and MetaHuman outputs as AI-training inputs. That prospective EULA change is separate from permission to use *Fortnite* IP.

The reported events therefore combine two different boundaries. One is a contractual boundary concerning whether engine or character-tool output can be used for training. The other is the copyright and trademark boundary around a game property and its distribution. Removing or changing the first would not, on the supplied reporting, authorize the second.

## What the archive adds
This is a new enforcement fact on a known story. [Our earlier Field Note on AI-made browser versions of legacy games](https://newruntime.com/posts/claude-is-reportedly-turning-old-console-hits-into-bf574f/) argued that AI-assisted reconstruction could make repeated copies cheaper and shift the challenge toward containing them. The reported Microsoft and Epic notices are an early example of that containment response. A separate [Field Note on Epic's reported AI-first game-development direction](https://newruntime.com/posts/epic-games-told-the-team-making-its-marvel-1021b8/) supplies relevant context: the same company is reported to be adopting generative AI in production while enforcing its game IP.

## Trend signal
No supplied site pattern genuinely fits this event closely enough to support a trend claim. The report is principally about IP enforcement around reconstructed software, not a demonstrated change in agent architecture, protocols, security, economics, or organizational design.

## Why now
Kotaku places the notices in a recent surge of AI-assisted decompilation, browser ports, and recompilations. Its account is that the volume and speed of new projects have increased sharply enough that publishers are now responding with repeated DMCA actions. The timing of Epic's October 10 notice and the October 27 update makes the story a current enforcement development rather than a general debate about training data.

## Connections to other events
The connection to the archive is direct rather than speculative. The earlier legacy-game report documented browser-playable reconstructions of *Halo: Combat Evolved*, *Grand Theft Auto: Vice City*, and *The Simpsons: Hit and Run*. The new report says Microsoft notices have included *Halo*-related browser ports. It also meets the earlier report on Epic's reported use of Claude in a Disney/Marvel game project: both concern how a publisher navigates generative AI, but one is about adopting AI in production and this one is about limiting unauthorized use of its own IP.

## Why it matters
Teams using coding agents can now make compatible implementations, migrations, reconstructions, and interface replicas faster than before. That speed can create a misleading sense that technical feasibility is the remaining obstacle. This episode is a reminder that the deployable product boundary is wider than generated code. It can include copyrighted source and assets, trademarks, contractual restrictions, distribution rights, and the practical risk of a platform-level takedown.

For legitimate work, the useful response is not to avoid automation. It is to put provenance and authorization into the build path: identify which inputs are owned, licensed, independently created, or merely observed; record the intended compatibility boundary; and review names, art, audio, and data separately from the generated implementation. An agent can help reconstruct behavior, but it cannot confer permission to ship a reproduction.

## What happens next
- **More notices will target prominent browser ports and recompilations of recognizable game properties.** (3 months, 70%). Watch for: new DMCA-log entries and removals from public code hosts.
- **Teams will separate AI-assisted clean-room or compatibility work from ports that reuse protected assets and branding more explicitly.** (6 months, 55%). Watch for: project documentation describing provenance, replacement assets, and authorization.

## Limits and uncertainty
This Field Note relies on Kotaku's reporting and its summary of DMCA-log entries; the supplied material does not include the notices themselves, a full project list, or responses from Microsoft. A DMCA notice is an enforcement action, not a court ruling on infringement, fair use, or the legality of decompilation. The source also does not establish how much AI contributed to any individual port, whether a project used original assets, or what happened after each notice. Its broader criticism of publishers' AI practices should not be treated as proof of the legal merits of the takedowns.

## Skill to build now
Add a provenance review to any agent-assisted compatibility or migration project this week. Make a short inventory with four columns: code origin, assets and data origin, names and branding, and distribution permission. For every generated artifact, assign an owner who can answer whether it is independently produced, licensed, replaced, or authorized. This is concrete operational work: it creates a release gate before a public repository, demo, browser deployment, or marketplace submission turns a technical experiment into a distribution event.

## Reader takeaway
AI-assisted reconstruction is making old software easier to reproduce, but it is not making that reproduction automatically shippable. The reported Microsoft and Epic notices show that rights, provenance, and permission remain product constraints. Treat them as part of the engineering specification from the first agent task onward.

## Open question
Will publishers provide licensed pathways for AI-assisted preservation or compatibility work, or will enforcement remain the primary response as reconstruction gets cheaper?

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)