Epic Games' AI-First Disney Shooter Delay

Epic's 'AI-first' mandate on the Disney shooter is not an isolated experiment - it is the visible edge of a retooling Tim Sweeney says touches every team at the company. In his own words: 'We have a huge pivot underway here at Epic, moving developers around to retool for maximum AI acceleration... and to bring the benefits to all teams using Unreal.' ^[1]That last clause matters: if the benefits are meant to reach 'all teams using Unreal,' the mandate isn't scoped to one Marvel-and-Star-Wars project, it's a bet on Unreal Engine's own tooling future. Communications director Jake Jones backed the framing publicly, describing the shift as 'embracing AI-accelerated development, led by Epic developers who are the visionaries and creative drivers.' ^[2]Sweeney has also cast the move in survival terms rather than efficiency terms: 'Our more modest aim is to survive the AI revolution, help other developers do the same, and come out on the other end making better code and content faster.' ^[3]That company-wide framing lands against an industry backdrop trending the opposite way on sentiment. GDC's annual State of the Game Industry survey found 52 percent of developers now believe generative AI is harmful to the industry, up from 30 percent a year earlier and just 18 percent two years ago. ^[4]Epic is pushing toward 'AI-first' at the exact moment the people who would have to live with it are souring on AI the fastest.

Before Epic ever told developers to stop writing code, the Disney shooter was already late. Reporting indicates 'Epic reportedly underestimated both the number of employees and the amount of time the project would require' ^[6], a staffing shortfall separately framed as Epic only turning to AI after the project had slipped. ^[5]The shooter had been 'supposed to release in March 2027' but 'has now been delayed due to slow progress and understaffed teams,' with no new date announced. ^[7]Only after that slip did a game director tell the team to 'stop using handwritten code'^[2], directing staff toward an 'AI first' production model built on Anthropic's Claude ^[8], with all art to be 'generated with full AI workflows.' ^[2]The sequencing matters for how the story gets read: this isn't a studio using AI to hit an aggressive timeline, it's a studio that had already missed its timeline reaching for an unproven production model as the fix. Whether AI-only workflows can actually recover lost schedule, rather than add a new layer of churn while developers relearn how to build the game, is untested at this scale.

The directive drew immediate skepticism from the people closest to the work. Developers on the project reacted with 'confusion and shock' ^[7], and 'jokes surfacing about whether errors made by Claude would have to be fixed by Claude.' ^[5]Outside the studio, commentary has focused on a specific technical worry: 'many commenters question whether a complex AAA game can be properly developed without human-written code, noting that debugging and making changes later in development could become particularly problematic.' ^[7]That skepticism mirrors a broader industry mood: a separate survey found 52 percent of game developers say generative AI is having a negative impact on the industry ^[9], and Epic's own directive - no hand-written code at all, not merely AI-assisted code - goes further than what most of that 52 percent were likely picturing when a studio says it is 'going AI-first.'

The AI-first mandate arrives roughly seven months after Epic laid off more than 1,000 employees, about 20 percent of its workforce, citing a Fortnite engagement downturn. ^[10]That round of cuts was paired with over $500 million in identified cost savings across contracting, marketing, and open roles ^[11], even as Disney's $1.5 billion, multiyear entertainment-universe investment in Epic from 2024 was publicly reaffirmed as still moving forward. ^[12]Sweeney's insistence that the AI pivot is about building 'MORE and BETTER stuff' rather than cutting headcount is a hard sell against that timeline: workers see a studio that shed a fifth of its staff for cost reasons, then told the remaining developers on its highest-profile unannounced project to stop writing code by hand. Whether that reads as efficient reallocation or as cover for further headcount reduction is exactly the fight playing out among the developers now expected to retool around Claude.