Enjoying this article? Add us as a preferred source on Google.
Blueprint is going away. At the opening keynote of Unreal Fest Tokyo 2026, held November 3 and 4, 2026 at TFT Hall in Ariake, Tokyo, Epic Games CEO Tim Sweeney announced that Unreal Engine 6 will drop Blueprint from day one and consolidate all gameplay scripting into Verse. Then, standing on that stage, Sweeney apologized to the developers in the room for killing Blueprint.
This is a reversal of the plan Epic laid out only months ago. Back at Unreal Fest 2026 in Chicago in June, the roadmap was a staged migration: keep Blueprint in the early builds of UE6, then deprecate it once the Verse-centric pipeline had matured. That has now become “it isn’t shipping at all.”
Sweeney gave a single reason for the change: Epic found that text-based code is vastly more productive for AI than Blueprint. He explained that the company made the call to strip Blueprint out of the UE6 development environment, which launches at the end of 2027.
If you grew up wiring nodes together to build logic, this one lands hard. So what’s actually confirmed, and what’s being offered in Blueprint’s place? Here’s what the keynote laid out.
What happens to Blueprint in Unreal Engine 6?
Blueprint is being removed from the UE6 development environment. Gameplay scripting consolidates into Verse, while C++ continues to be the language of the engine itself.
The key detail is how clearly the position shifted between June and November. Put the two side by side and the gap is obvious.
| When | Blueprint’s status |
|---|---|
| June 2026 (Unreal Fest 2026, Chicago, USA) | Kept in early UE6 builds, deprecated once the Verse-centric pipeline matures |
| November 2026 (Unreal Fest Tokyo 2026) | Gone from UE6 from day one, with gameplay scripting consolidated into Verse |
UE6 launches at the end of 2027. For developers sitting on existing projects, that works out to roughly a year of runway from this reversal. Epic says AI-assisted conversion tooling will be provided for the migration, so this isn’t a demand that anyone hand-rewrite node graphs into code line by line.
Why did the plan change? It comes down to AI productivity
The reason Sweeney gave is that text-based code turned out to be far more productive for AI to work with than Blueprint.
Say it out loud and it tracks. Node graphs are excellent for humans parsing logic visually, but they’re a terrible fit as something you hand to an AI to read and rewrite. Text diffs cleanly, and it’s easier both to generate and to verify. Blueprint didn’t get cut to suit the engine, it got cut to suit a development flow that assumes AI.
Internally, Epic says AI has already delivered productivity gains of 1.5x to 4x. The company expects at least 4x by the end of 2026 and 10x across many areas by mid-2027. If you’re seriously chasing numbers like that, standardizing the input format on text is the rational move.
Developers will be able to connect whatever AI model they prefer by way of MCP servers or Python scripting interfaces. Epic isn’t building its own models. It plans to partner with AI companies in the US and China and supply data so that each firm’s models get better at 3D. The division of labor there is refreshingly blunt.
What kind of language is Verse?
Verse is positioned as a language that’s as approachable to write as C# while being as powerful as C++. It’s already in use in UEFN (Unreal Editor for Fortnite), and in UE6 it gets promoted to the scripting language for everything.
Which means Verse is something you can touch today. There’s no reason to sit around waiting for UE6’s late-2027 launch. Whether you keep the muscle memory of dragging wires or start shifting toward writing text now, your position a year from now is going to look pretty different.
What success stories and numbers did the keynote put up?
The keynote highlighted Sonic Racing: CrossWorlds as a success story out of Japan. It sold more than a million copies in its first month, and the relationship has extended into Sonic showing up in Fortnite.
Epic also pointed to Meccha Chameleon, a game built by two developers who learned their craft in UEFN and went on to sell 20 million copies on Steam. The framing was clear: UEFN isn’t just a playground inside Fortnite, it’s a front door to commercial releases.
| Metric | Figure |
|---|---|
| Fortnite MAU | 76 million |
| Roblox MAU | Over 400 million |
| Steal the Brainrot (team of 7) | 4.5 million MAU / 1.1 million concurrent during a live event |
| Paid out to developers since the UEFN launch | Over $1 billion cumulative |
| Sonic Racing: CrossWorlds | Over 1 million copies in the first month |
Steal the Brainrot is run by seven people, and they push live events at the 1.1 million concurrent scale without having to provision servers or handle the ops themselves. That’s the heart of what Epic wants you to see: scaling is the platform’s problem, not yours.
The monetization side is just as concrete. Pay 20% of revenue to the IP holder and you can build content using Star Wars or LEGO without negotiating an individual contract. For solo developers and small teams, the tallest wall in the business, rights clearance, has been replaced by a pricing rule.
What happens to existing projects? The reality of migrating
Epic says AI-assisted conversion tooling will be provided for moving from UE5 to UE6. As of November 2026, no concrete figures on conversion accuracy or coverage have been published.
This is the part where neither optimism nor doom is justified yet. The deeper a project’s logic is built in Blueprint, the harder the conversion is going to be, so it’s early to expect “press one button and it’s all Verse.” On the other hand, since Epic decided on removal with migration tooling as a premise, it’s hard to imagine developers being left hanging entirely.
The practical stance is a simple split: write anything new in Verse, and keep existing work on UE5 until real information about the conversion tooling shows up. Sweeney apologized because he knows exactly how much work this dumps on developers.
Enjoying this article? Add us as a preferred source on Google.
Summary: UE6 arrives at the end of 2027, and Blueprint isn’t in it
At the opening keynote of Unreal Fest Tokyo 2026, Tim Sweeney announced that UE6 will drop Blueprint from day one and consolidate gameplay scripting into Verse. C++ remains the language of the engine itself.
The reason for the reversal is that text-based code proved far more productive for AI, and the decision was made to strip Blueprint out of the UE6 development environment launching at the end of 2027. In Chicago in June, the line was “it stays in the early builds,” so this flip took only a few months. Sweeney apologized to the developers in the room.
AI-assisted conversion tooling will be provided for the UE5 to UE6 migration. Verse already works in UEFN, so you can start on it right now. If that 10x productivity target is genuine, funneling everything through text was probably always where this was heading.
Blueprint was the symbol of a promise: you don’t have to be a programmer to make a game. Folding it up to suit AI looks brutal, but the logic holds. Paired with an AI, someone who can write text really is faster than someone who can wire nodes. Attaching an apology to the news reads as an acknowledgment that Epic understands the pain it’s causing.
UE6 lands at the end of 2027. Verse is writable today. You have a year.
Read Next
Nokko Oda
Leave a Reply