Epic Games has revealed that a decade-old, hard-to-reproduce bug in the Unreal Engine codebase has been "almost completely eliminated," and that AI coding tools now write the majority of the engine's code. Around October 30, Marcus Wassmer, Epic's Executive Vice President of Development, told the outlet This Week in Videogames that AI tools—naming Claude Code and Codex—were the main force behind the fix, across the Fortnite, Unreal Editor for Fortnite, and Unreal Engine 6 development streams.
"Yes, we are vibe-coding things"
Wassmer acknowledged directly: "Yes, we are vibe-coding things," meaning "our engineers no longer write the majority of the code, but they still steer the tools to get the architectural outcomes we want." He emphasized Epic iterates with AI rather than "generating the entire engine in one shot," with engineers watching three envelopes: memory, performance, and scalability. The engineer's role shifts from typing code to drawing boundaries, reviewing output, and defining architecture.
Track record: a ten-year bug and a one-week rewrite
| Achievement | Context | Result | |---|---|---| | Non-deterministic cooking bug | Chased for ~10 years, no regular reproduction | Almost completely eliminated | | Shader compression | Patch sizes long too large | Significantly reduced | | D3D12 rendering-layer rewrite | Estimated 3–6 weeks for one engineer | Done in ~1 week, better CPU time, fewer bugs | | Internal test suite | Insufficient coverage | Healthy and expanding coverage | | Fortnite PC stability | Manual troubleshooting | Automated monitoring, root-cause analysis, and fix generation |
Note the caveats: the D3D12 comparison is against Wassmer's own prior estimate—two people's time estimates can differ widely, so this is not a controlled experiment. The cooking-bug "elimination" also lacks third-party reproduction reports; it is currently vendor self-reported.
The risk of moving slowly
Asked about AI skepticism, Wassmer said: "We are more worried about the risk of moving too slowly than about AI skepticism." This matches Tim Sweeney's recent confirmation on X that Epic uses AI tools to develop Unreal Engine code, and Epic's announcement earlier this month removing clauses prohibiting AI training on Unreal Engine and MetaHuman output—with Sweeney simultaneously criticizing Steam's AI disclosure labels. Notably, Epic's June UE6 roadmap still stated that "most code-generation use cases have not entered mainline code"; months later, Wassmer's claim has advanced to "most code written by AI."
Why this matters
- This is one of the first AI-coding production reports from a first-tier engine vendor, specific down to bug names and week counts—readable and auditable, unlike benchmark leaderboards.
- "Vibe coding" debates have mostly centered on toy projects and personal productivity; this involves mainline production in a codebase of tens of millions of lines of C++.
- Risks remain concrete: UE5 community criticism of performance and stability is long-standing, and whether AI-accelerated delivery addresses it awaits UE 5.9 and UE6. Self-reported wins and independent verification are still one release cycle apart.
Sources and limitations: This Week in Videogames interview (Wassmer); October 30 reports from PC Gamer, Rock Paper Shotgun, and iXBT; Tim Sweeney's confirmation on X; UE6 roadmap published by Epic on June 22. All headline figures (ten years, 3–6 weeks, 1 week) are Wassmer's self-reported statements, not third-party audited; the cooking-bug fix has no independent reproduction; exact dates of Sweeney's statements vary slightly across reports.