Epic's AI-coded engine needs proof before it needs trust

Epic Games has confirmed that its engineers are “vibe-coding” Unreal Engine 6 and future Fortnite updates, as Polygon reported on Wednesday.¹ The company’s executive VP of development, Marcus Wassmer, put it plainly in a statement to This Week In Video Games: “Yes, we are vibe-coding things.”¹

Here is my argument in one sentence: using AI to write engine code is not the scandal, but asking developers to take it on faith is, and Epic should answer with proof instead of confidence.

Start with what Epic actually said. Wassmer says engineers no longer write the bulk of the code but still guide the tools toward the architecture they want. He says the team is not “one-shotting” the engine, and is instead iterating with AI to ship features developers want while keeping the engine within its memory, performance and scalability limits.¹ That is a more careful claim than the phrase “vibe coding” suggests, and it deserves to be read as stated.

Now the best case for Epic. Wassmer says the company is more worried about moving too slowly than about AI skepticism.¹ A commenter under the Polygon story made a similar point, arguing that coding teams across industries work this way and that done properly it beats the old methods.¹ If the output is reviewed, tested and held to hard performance limits, who typed it matters less than whether it works. Nobody asks which keyboard wrote a good function.

I take that argument seriously, and I still think it falls short, because of the track record. A year ago, Tim Sweeney denied the company was using AI for Unreal Engine updates.¹ This month Epic said it vibe-coded a new Epic Games Store launcher, after which clips of the launcher hallucinating spread online, and one poster claimed it had bricked their PC.¹ Epic said the launcher booted faster than Steam, and a Valve store update soon erased the gap.¹ Those are claims from social media and a company boast, not audited findings, but they are the evidence we have. A studio’s record is evidence, and so far Epic’s record on this topic is a reversal and a shaky launcher.

There is a second, quieter issue. Polygon notes that many developers are alarmed at the idea of an engine “vibe-coded” by AI that may not be fully understood by Epic.¹ Those developers build on Unreal and ship products on top of it. If a bug surfaces deep in the engine, they need to know someone at Epic can read the code and explain it. That is the promise behind a licensing fee, and it is the one Epic needs to renew.

Our read: The method is not the problem; the lack of visible accountability is. What would change my view is concrete: published testing and review practices for AI-written engine code, performance benchmarks developers can verify, and a clean first year of Unreal Engine 6 releases without the kind of launcher stumbles we just watched. If Epic shows its work, I will happily say the worry was overblown.

Until then, the lesson is an old one. Speed is easy to announce, and trust is the only part you have to earn.

Footnotes

1. Polygon, “Epic Officially Confirms It’s ‘Vibe Coding’ Unreal Engine 6 and Future ‘Fortnite’ Updates”. Retrieved October 28, 2026. ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷ ↩⁸ ↩⁹