Epic says AI writes most of Fortnite's code. Who answers when it breaks?
Epic's admission that engineers no longer write most of the code in Fortnite and Unreal Engine 6 is candid. It also leaves players with accountability questions the studio hasn't answered.
AI-generated image
Is it progress when a studio tells you, proudly, that its engineers no longer write most of the code in the game you play every day? Or is that the moment to ask who is actually responsible for it? Epic Games has just made that confession, and we think the confession is the least interesting part.
What Epic actually said
Marcus Wassmer, Epic's executive vice president of development, has explained how the company works on Unreal Engine 6, Fortnite and other projects. His blunt summary, as skoar.gg quotes him, was "We're vibe-coding now." Engineers, according to Softonic's account, steer the tools toward the architecture they want. They then test and refine the output so memory use, performance and scalability stay on target.
Epic also points to results. A report from Game Developer says an Epic VP claims AI code tools stomped out decade-old "non-deterministic cooking bugs" in Unreal Engine. And Rock Paper Shotgun's headline carries Epic's stated worry: it is "more concerned about the risks of moving too slowly".
Honesty is a virtue, but it isn't an answer
Credit where it's due. Plenty of studios use these tools and say nothing. Epic said it out loud, and that makes it easier to judge. We also think the "engineers steer, test and refine" framing is reasonable. If that's literally how it works, the human job has moved from typing to reviewing, which is a legitimate change in craft.
But "we review it" is a claim, not a guarantee. Nothing in the material we've seen explains how much review happens, who signs off on code a tool produced, or what happens when a Fortnite update ships a regression that nobody on the team fully wrote. The decade-old bug story is a good anecdote. One fixed bug doesn't show that the whole pipeline is healthy, and it says nothing about the new bugs this approach could introduce. We'd call the speed argument the easy half. The hard half is accountability, and Epic hasn't given it the same airtime.
Unreal Engine makes this more than a Fortnite issue. Engine code ends up inside other studios' games. If the engine is increasingly machine-written, every licensee inherits that decision, and they deserve to know how it's being verified.
A studio asking for trust while spending it
The timing doesn't help. The recent weeks around Epic have been noisy. Tim Sweeney has defended AI at the company and taken heavy criticism, according to 3DJuegos. The same piece reports Epic is working to remove the Unreal Engine and MetaHuman EULA restriction on using their outputs to train AI models. Sweeney says each studio could set its own terms, while Fortnite itself couldn't be used to train third-party models or be copied via AI without permission.
Look at the shape of that position. AI should flow freely into Epic's tools and workflow. Fortnite's own content should stay fenced off. We're not saying that's hypocritical, because protecting your own IP is normal. But it does mean Epic's enthusiasm for the technology has clear limits when the technology points back at Epic. A studio that wants players and developers to trust its AI-heavy process can't also treat every question about it as a political attack. Sweeney's complaint about Steam's AI disclosure, which he called a "political statement", sits awkwardly next to this. Disclosure is exactly what Epic is now practicing about its own code, and it's what players are entitled to.
What we'd like to see
This is our view, not a prediction of what Epic will do. We'd want three things in public:
- A plain description of the review process for machine-written code, and who is accountable for it.
- Data, not anecdotes, on whether stability and performance in Fortnite and the engine improve or slip over the coming releases.
- A clear statement of how the licensing changes will affect developers who build on Unreal Engine.
Epic isn't wrong to use these tools, and we don't think the future of game development is hand-typed code. The mistake would be treating the announcement as the finish line. "The AI wrote it" can't become the answer to "why is this broken?" Players and developers should hold Epic to its own transparency, and the first patch that goes badly wrong will be the test.
No topics yet: start the first one.
More stories
Rockstar's union vote around the GTA 6 launch is leverage, not luck
Holding the ballot around GTA 6's release looks built for maximum visibility, and it turns the industry's most secretive studio into a labor test case players should watch.
Pulling the demo is rational, but it's a bad equilibrium for everyone
Indie studios are canceling demos because AI can clone a game from a short clip. Their fear is justified, but silence will starve discovery, and the industry needs rules.
Mass Effect can outlive BioWare, but only if EA lets go
With BioWare shut and Mass Effect 5 cancelled, the petitions and the support from voice actors and veterans show what the IP is worth. EA's track record suggests it will sit on it.
Rockstar wants to be faster, but speed was never in its DNA
Rockstar says its next game won't take another eight years. It's the right instinct, but a studio built on obsessive detail will have to prove what it's willing to give up.



