Epic Is Vibe Coding Unreal and Fortnite. As a Senior Developer, I'm Glad.

Epic Games is done being quiet about AI. On October 25, Tim Sweeney replied to a developer on X: "Yes, we are now using AI tools to develop code for Unreal Engine." Two days later, Epic's executive VP of development, Marcus Wassmer, went further in a statement to This Week in Videogames: "Yes, we are vibe-coding things."

The reaction was about what you'd expect. Plenty of gamers and developers hate it. PC Gamer's take was that the whole idea gives its writer a stress headache, in part because of "the comment-less form AI-assisted code can often take."

I get the nerves. I just don't share them. I'm a senior software developer, I use AI agents every working day, and I'm a heavy PC gamer the rest of the time. From both seats, this looks like good news.

Read the full statement and it isn't a CEO waving his hands about the future. It's specific. Wassmer says the engineers "are no longer writing the bulk of the code, but they are still guiding the tools to get the architectural result we want." He also says, "We're not 'one-shotting' the engine; we're iterating with AI," while keeping it inside its "memory, performance, and scalability envelopes."

That's the right way to do it. It's also how I work. I don't type "build me an app" and ship whatever comes back. I describe the change, point the agent at the patterns already in the repo, read the diff, run it and push back when it's wrong. The agent does most of the typing. I still own the architecture and the decision to merge.

Epic could have kept this quiet. Wassmer's closing line is basically the opposite: "We think it's best to just be up front with what we're doing, share best practices with other developers." I'll take a studio that tells me how it builds over one that pretends it doesn't use the same tools everyone else does.

The examples Wassmer gave aren't flashy features. They're the kind of grinding engineering work that never gets done because there's never time:

• "Almost the complete elimination of non-deterministic cooking bugs which we've been fighting for a decade."
• Faster work on shader compression, which he says helps cut patch sizes.
• A rewrite of a big chunk of the D3D12 rendering layer that he estimated at three to six weeks for one engineer, done in "about one week with a nice win on CPU time and fewer bugs."
• Monitoring PC stability in Fortnite to catch bad driver and hardware combinations that "would previously have taken months to root cause."
• Large refactors touching "thousands of files in relatively minor ways," which he says were too big to do by hand.

That list lines up with my own experience. The best AI work I do isn't the shiny new feature. It's the cleanup I've been putting off for months: tracing an inherited app, untangling a migration, adding test coverage nobody budgeted for, or applying the same careful change across fifty files without missing one.

As a gamer, that's the part I care about. Smaller patches. Fewer weird crashes on my exact GPU and driver combo. Bugs that have been around for a decade finally getting fixed. If AI tools are how that happens, great.

This is where I disagree with PC Gamer most. In my day-to-day work with Cursor and Grok Bot, the problem has never been too few comments. If anything, it's the opposite.

The agents I use explain themselves constantly. A new function shows up with a docblock saying what it takes, what it returns and why it exists. A tricky branch gets a comment explaining the edge case it handles. A security fix notes what it's guarding against. The pull request summary walks through every change in plain English. Some days I'm trimming comments, not adding them.

Here's the kicker: it beats a lot of the human-written code I've inherited. I've opened plenty of legacy apps where the only comments in a huge file were commented-out blocks nobody dared delete. AI didn't invent commentless code. People have been shipping it for decades.

And when you want more, you ask. Put your standards in the project rules, like "document every public function" or "explain why, not what," and the agent follows them every single time. A tired developer at 6 PM on a Friday won't.

Most of the fear around vibe coding comes from the lazy version: someone prompts an app into existence, never reads it and ships it. That's a real problem. It's a process problem, though, and it isn't new. Copying code off a forum and shipping it without reading it is the same mistake.

Used correctly, these tools work like a very fast teammate who never gets bored of the boring parts. You still review everything. You still test it. You still decide what's allowed to touch production. Done that way, it's not more dangerous than a junior developer's first pull request, and it's often a lot cleaner.

I'm not saying there's nothing to watch.

Previews will be rough. Epic's own launcher post called the new vibe-coded launcher "light on features." Early builds of anything have bugs, AI-assisted or not.

Speed can tempt teams to skip review. That's the real risk. The tool won't skip review on its own. People skip it.

Trust has to be earned. Wassmer said it himself: the best answer to skeptics is "the quality of the games and tools we're able to deliver."

All three of those come back to the same thing: keep humans in the loop and judge the results.

I'm going to judge Epic the way I judge my own work: by what ships. If Unreal Engine 6 shows up more modular, more stable and quicker to patch, the argument is over. If it doesn't, the tools won't be the reason. The process will.

For me, nothing about the job changes. I still decide what gets built, how it fits together and whether it's good enough to ship. The agents just get me there faster, with better comments than I'd have bothered to write.

• This Week in Videogames, "Epic Games Confirms AI is Being Used to 'Develop Code and Features for Unreal Engine'"
• Tim Sweeney on X: "Yes, we are now using AI tools to develop code for Unreal Engine."
• Epic Games Store on X: "We vibe coded the Epic Games Launcher to be faster than the other guy."
• Epic Games Store, "The new Epic Games Launcher is finally here in Preview"
• PC Gamer, "'Yes, we are vibe-coding things': Epic confirms it's using AI tools to code Unreal Engine 6, Fortnite, and more"