Per a Bloomberg report, Epic Games has delayed an unannounced shooter featuring Marvel and Star Wars characters — previously expected in March 2027, now with no communicated date — and instructed the development team to rebuild its production model around AI tools, covering both code and artwork.
One of the game’s directors told the team, in the quote that is going to follow this story around: “No more hand-written code.” The stated expectation is that developers edit and guide AI agents, with tools including Anthropic’s Claude.
Tim Sweeney confirmed the broader change publicly shortly after the report:
“We have a huge pivot underway here at Epic, moving developers around to retool for maximum AI acceleration.”
Why the sequencing matters more than the directive
The directive on its own is a management decision a company is entitled to make. The sequence is what makes this a story.
In March, Epic laid off more than 1,000 employees — roughly 20% of its workforce — after Sweeney acknowledged that declining Fortnite engagement had Epic spending substantially more than it earned. The company identified more than $500 million in further savings across contractors, marketing and unfilled positions, explicitly said the layoffs were not caused by AI, and framed the restructuring as funding the transition to Unreal Engine 6 and the next Fortnite ecosystem.
Seven months later, a project is behind schedule — Bloomberg’s sources say partly because Epic underestimated how much time and staffing it would require — and the response is an AI-first production model.
Sweeney’s framing is that this is additive:
the objective is not to produce the same amount of work with fewer employees, but to help Epic’s existing teams create more
And Communications Director Jake Jones:
“We’re embracing AI-accelerated development, led by Epic developers who are the visionaries and creative drivers for everything we do.”
Those statements may be entirely sincere. They also sit immediately next to “we underestimated the staffing this needed” and “we removed 20% of the staff,” and the two readings are hard to separate from outside. 80 Level’s own assessment is the fair one: the proximity will intensify questions about whether these tools are supporting teams or compensating for resources removed through restructuring.
This was on the roadmap
It is worth being clear that this is not a sudden reversal. Epic has been building toward it in public:
- Unreal Engine 5.8 introduced experimental MCP-based integrations letting language models interact directly with editor workflows
- At State of Unreal, AI-assisted development was positioned as a component of Unreal Engine 6, alongside Verse, interoperable assets and deeper Unreal-to-Fortnite connections
Sweeney also says the intent is eventually to extend these capabilities to developers using Unreal Engine — which is the part that reaches past Epic. If the engine ships with agent-driven workflows as a first-class path, that is the default production model for a very large share of the industry, not one studio’s internal policy.
”No more hand-written code” is a specific claim, and the specific problems are known
Set aside whether it is a good idea. The engineering objections to it are not speculative, and 80 Level lists them accurately: maintainability, authorship, training data, consistency, and the ability of developers to understand and control generated systems.
The one that bites hardest in games specifically is understanding and control. A game is a system whose emergent behaviour is the product — the thing you ship is how a thousand interacting rules feel at frame 40,000 of a play session. Debugging that requires a mental model of code you did not write, in a codebase where nobody has that model because nobody wrote it. “Edit and guide AI agents” describes the authoring step and says nothing about the eighteen months of fixing that follows.
And the second: consistency. Generated systems are locally plausible and globally divergent. Two agents solving two adjacent problems will solve them differently, and the cost shows up as integration work — which is the thing that was already behind schedule.
It is not unusual, and that is the other half of the picture
AI use inside game studios is now ordinary. A recent CESA survey found 85.8% of participating Japanese developers use generative AI.
So the thing that distinguishes this is not that Epic is using AI. It is the absolutism of “no more hand-written code”, applied as a directive, to a team that is already late, by a company that has recently removed a fifth of its people — and the fact that the same company controls the engine a large part of the industry builds on.