Epic is right to rip Blueprints out of Unreal Engine 6 instead of keeping two gameplay systems alive. A clean break beats a decade of hybrid projects. The date small teams should circle is not UE6’s release, though. It is the day UE5 stops getting real updates.
What Epic announced in Tokyo
At Unreal Fest Tokyo on November 3, Tim Sweeney showed keynote slides that marked Blueprints, Actors and the C++ Gameplay Framework as “Remove” rather than deprecated. They will be gone from the start of UE6 Early Access, which is still planned for the end of 2027.
That reverses the June plan. Back then, Epic said Blueprints would be supported in Early Access and the initial UE6 releases and deprecated later.
Gameplay in UE6 moves to Verse, the language Epic already runs in Unreal Editor for Fortnite. Scenes move to Scene Graph, which builds things from entities and components instead of Actors. Building through MCP and Python becomes standard, and C++ stays in the lower layers like rendering and physics.
Sweeney apologized to the many developers who love Blueprints and called it a painful change. “While it will be painful at first, subsequent productivity will greatly improve,” he told developers, according to Famitsu’s report.
Why we think Epic is right
The reasoning is AI, and Epic isn’t coy about it. Sweeney said AI has made Epic’s own programming, debugging and level design 1.5 to 4 times more productive. Text code is something models can read and write. Node graphs mostly aren’t.
His case against a hybrid is the most persuasive part. Keeping old and new systems side by side tends to produce “a giant tangle of blueprints and verse, actors and entities,” he wrote on X. He added that AI assisted conversion “will produce a way more manageable UE6 project than a hybrid.”
We agree. Anyone who has opened an old project with three generations of half migrated systems knows that tangle well. A long overlap sounds kind. In practice it becomes a permanent, Byzantine middle ground that every tutorial, plugin and hire has to navigate.
Epic is also eating its own cooking. It plans to prove the approach by converting Fortnite, the game with the largest base of Blueprints in existence. That is a serious hostage to fortune for a live game with that many players.
And the model choice stays open. Sweeney said you can use any model or no model without Epic getting in between.
What it costs small teams
None of that makes the pain imaginary. Blueprints are how artists and designers touch gameplay in Unreal. One longtime user on Epic’s forums warned the plan will cause “animosity and distrust in the indie community”.
There is no node graph waiting on the other side either. Andrew Grant, a lead developer on UEFN, said there are “no plans” for a visual version of Verse. Older explainers that promise one are out of date.
Then there’s the bill. Epic’s conversion tools will use AI, and their format hasn’t been decided. One indie developer put the question bluntly, asking “who is going to pay for all this AI?” A free engine that leans on paid models is a different deal for a team of three.
The models aren’t fluent yet. Sweeney said leading models saw little Verse in training, “but that will change by January.” Many of us were hoping to learn Verse by January too.
The UE5 clock
Every explainer we’ve read says to stay on UE5 for now. That’s sound advice for a game shipping soon. What most skip is how long “for now” lasts.
Sweeney was explicit. “After UE6 preview 1 launches, we won’t be continuing UE5 development except for critical security and platform compatibility fixes,” he wrote. UE6’s full release is targeted 12 to 18 months after Early Access, but UE5’s feature work ends well before that.
So UE5 is not a slow, sanguine fade. It’s a branch that keeps running while the engine’s attention moves elsewhere. Projects already in production can stay on UE5. New features, new AI tooling and new platform work will inexorably land on UE6.
The near term is busy. Epic says Unreal Engine 5.9 arrives in Preview this week, with improved AI workflows and web as a target platform. Sweeney also called Epic’s push “all in.” In his words, “AI won’t un-happen.”
What to do now
These steps are cheap, and most are worth doing even if UE6 slips.
Finish what you’re shipping on UE5. Pin your engine version for any game due in the next two years. Don’t plan a UE6 move mid project.
Put the UE5 freeze on your calendar. Treat the first UE6 preview as the point where UE5 only gets critical fixes. A long running live game should plan its migration window around that, not around 2029.
Spend a weekend in UEFN. Epic Games Japan head Takayuki Kawasaki urged developers to try Verse and Scene Graph in UEFN first. Epic’s Verse lessons are free and built for beginners.
Point your AI at the docs. Sweeney says models become fluent when you point them at Epic’s documentation and samples. Keep the Verse language reference in your assistant’s context until the models catch up.
Tidy your Blueprints before anyone converts them. Small, well named functions with clear inputs and outputs will survive an automated rewrite far better than one sprawling graph. Keep tuning values in data tables and data assets, not buried in nodes.
Budget for the conversion. Track what your AI coding tools cost you per month today. Converting a large project will use far more, and Epic hasn’t said what its tools will cost or need.
Audit your plugins. List every Blueprint and C++ gameplay plugin your game depends on. Their authors face the same rewrite, and not all of them will make it.
Don’t panic about speed. Verse ran at Blueprint speed at launch. Sweeney says a new interpreter is 4x faster, with a future JIT adding another 4 to 5x, though it will stay slower than C++.
Read the 5.9 Preview notes this week. They’ll show how far the new AI workflows go before UE6. Our guide to the best AI tools for Unreal Engine covers what already works in UE5 today.
