Epic Games, the studio behind Fortnite, is reorganizing its development structure around AI. On October 12, 2026, CEO Tim Sweeney said on X that a major shift is under way to reassign developers in preparation for AI-accelerated development. The same day, Bloomberg reported that an internal directive had been issued to make AI central to code and art production on an unannounced game Epic is developing with Disney. Sweeney's stated goal is to raise the quantity and quality of what each developer can make, and to deliver those results to teams that use Unreal Engine as well.
Epic was already using AI in development. This change goes beyond whether to adopt it, extending to who builds what and how AI output is turned into a finished product. The key question is whether an internal shift can be turned into a production foundation that outside studios can use too.
"No more hand-written code" on the new Disney game
According to a report by Bloomberg's Jason Schreier on October 12, the project is an unannounced shooter featuring Marvel and Star Wars characters. It had been scheduled to launch the following March, but was reportedly delayed without a new date.
An internal message the reporter reviewed instructed staff to stop writing code by hand and to generate art assets entirely through an AI-driven production pipeline. The setup uses tools such as Claude, with humans managing the work and providing direction. What was reported is the production policy for this new game. It does not show that the same instruction was issued across the existing Fortnite.
The delay and the shift to AI cannot be tied together as simple cause and effect, either. Bloomberg relayed an explanation from people familiar with the matter that Epic had underestimated the staffing and production time required, and that progress was slower than expected. Epic spokesperson Jake Jones told Bloomberg that the company is adopting AI-accelerated development in which developers provide the creative direction. Whether AI can get the game finished remains to be seen.
The Disney partnership has a broader scope than this one game. In the joint vision announced on February 7, 2024, the companies said they would build a persistent entertainment universe on Unreal Engine, interconnected with Fortnite, where people could play, watch, shop, and create their own content. The $1.5 billion Disney announced is the amount of its investment to acquire an equity stake in Epic. Reading it as the development cost of a single new game would confuse the scale of the business with a production problem. Nor does the delay report imply the cancellation of the partnership as a whole.
What changed between June and October
In his June 22 explanation of UE6, Epic's head of engineering Marcus Wassmer said that development teams, from the backend to the engine to the games, had been given broad access to code generation and AI analysis. Examples of results included internal helper tools, root-cause investigation of failures, and test generation, and most were not uses that generated major code for Unreal Engine itself, he said.
Epic's public stance moved from using AI for supporting tasks in June to reassigning developers in October.
| Date / Speaker | AI use described | Change it suggests |
|---|---|---|
| June 22, 2026 · Marcus Wassmer | Broad use of code generation and analysis; most example results were supporting tasks | Rolling out uses that help with day-to-day development work |
| October 12, 2026 · Tim Sweeney | Reassigning developers, aiming to raise each person's output and quality | Announcing a shift in development structure that involves staffing |
The table pulls publication dates and target tasks from the official June document and Sweeney's own October post. It compares explanations of different scope, and it is not a timeline showing that a companywide transition has been completed or that productivity has risen.
Still, the explanation that even developer assignments will change is significant. Epic appears to be moving from a stage where support tools shorten existing work to one where work is divided on the premise of AI. The internal directive on the Disney project can be seen as exclusive reporting on how far that change reaches on the production floor.
The impact on Unreal Engine hinges on connecting to production tools
In the official UE6 plan, MCP is used to connect AI models to engine features. MCP is a common connection method that lets AI exchange information with external tools. Epic says it will make a wide range of engine features accessible this way and let developers combine the models of their choice.
Making a game takes more than writing code. In lighting adjustment, for example, someone has to apply the values a model suggests to the actual scene, check the screen, and revise. The idea of linking models and the engine aims to extend AI assistance to operating production tools themselves. The targets Epic officially names include level setup, character skeletons, and lighting adjustment.
For outside studios, this comes down to how to combine the models they want to use with their existing production environments. If Epic can turn methods it tried internally and in UEFN, the Fortnite editor, into features other teams can use, it may reduce the burden of building connections on their own. However, this is not a plan to require outside users to use a particular AI; it aims for a production environment where models can be chosen.
Delivery will also take time. The early-access target Epic set for UE6 in June is the end of 2027. Sweeney's October announcement about reassigning staff does not mean outside studios can immediately use the same production process. The work remains of turning internal results into tools people can actually operate and repeatable procedures.
Separate from layoffs, but financial pressure remains
In an internal memo on March 24, Epic announced cuts of more than 1,000 people. It explained that weak Fortnite engagement since 2025 had left spending well above revenue. Along with outsourcing and marketing, it said it also reviewed open positions it had planned to hire for, identifying more than $500 million in cost reductions. That figure is not savings from AI.
In the same memo, Sweeney stated explicitly that the layoffs were unrelated to AI. In his October post as well, he emphasizes that the aim is to enable the developers who remain to make more and better things, rather than to make the same things with fewer people. Reading both explanations, there is no basis to conclude that the March cuts were AI replacement.
At the same time, when a company rebuilding its finances changes how it produces games, how to recover revenue after increasing output is unavoidable. Even if AI can produce assets faster, they must still be assembled into a work, have problems fixed, and be finished into an experience players keep coming back to. This is a management challenge that follows from the new policy, not a result Epic has shown it has already solved.
The underestimation of staffing and time reported for the new Disney game bears on this judgment as well. If the production process is changed, both the speed at which AI generates and the time humans need to verify and correct must be re-estimated, or it is unclear whether the schedule can be restored.
How to verify the "3x" productivity outlook
In an additional reply on X, Sweeney explained that efficiency changes vary greatly by technical area, and predicted that a year from now few areas will be below 3x compared with January 2026. This is an expectation about the future, not a measured result showing that the time to complete a game has already fallen to a third. The posts do not say how efficiency is measured or how quality and the burden of rework are counted.
The difficulty of measuring developer productivity also shows up in a study by the research group METR. In an experiment described in a July 2025 research blog post, 16 experienced open-source developers worked on 246 tasks in their own repositories. When whether AI was allowed was randomly assigned per task, the tasks under the AI-allowed condition took 19% longer to complete. The study covered tools from February to June 2025, mainly Cursor Pro and the Claude models of the time.
This result cannot be applied to Epic today, however. It was not an experiment measuring game production, and the tool generation is different. METR itself acknowledged in a February 2026 update that newer tools may be making developers faster. At the same time, it explained that biases, such as developers who don't want to work without AI and tasks dropping out of the trial, along with the difficulty of measuring time when several tasks run in parallel, make it hard to confirm how much improvement there is.
Judging Epic's shift will likewise require more than the volume of generated code. The questions are whether time to completion, including verification and correction, gets shorter, whether product quality holds, and whether outside Unreal Engine users can reproduce the method on their own teams. If Epic can deliver on schedule and at quality on the new Disney game and carry that experience into usable production tools, its AI shift could prove useful for other studios' production as well.