At State of Unreal 2026 in June, Epic dropped a bombshell that the headlines mostly buried under the UE6 announcement: Blueprints are being deprecated. Epic is moving Unreal's gameplay programming model to a language called Verse, and the visual scripting system that defined the last decade of Unreal development is officially on the way out.
If you build in Unreal, this matters. Let me cut through the panic and the hot takes and tell you what is actually happening.
What Epic actually said
Here are the confirmed facts, straight from Epic's announcement and follow-up statements:
Unreal Engine 6 Early Access is targeted for the end of 2027. Full release lands sometime around 2028 to 2029. This is years out, not months.
UE 5.8, released alongside the announcement, is the last planned major UE5 version and the stable production target. What you build in UE5 today is what you ship with for the foreseeable future.
Blueprints and the Actor system will be available in early UE6 releases, then deprecated "when the new framework is sufficiently mature." Deprecated means it stops getting improvements and is eventually removed. Epic has promised conversion tools so existing projects are not stranded.
Verse becomes the primary gameplay scripting language. It was designed by Tim Sweeney and Simon Peyton Jones (one of the people behind Haskell), it has been running in Unreal Editor for Fortnite since 2023, and it draws from functional, logic, and imperative programming.
So nobody's project dies tomorrow. But the direction is set, and it is not changing.
Why Epic is doing this
Blueprints were brilliant for accessibility. They let designers, artists, and people without a CS degree build game logic by connecting nodes. That is genuinely valuable and it is a big reason Unreal got so popular.
But Blueprints have real problems at scale. They get messy fast. A complex Blueprint becomes a tangled wall of nodes that is hard to read, hard to review, and hard to maintain across a team. They do not play well with version control. You cannot diff them like text. And they hit performance ceilings that force you into C++ anyway.
Verse is plain text. That means it works with version control, code review, and the tooling real software teams depend on. Epic also designed it to handle massive, multiplayer, persistent worlds with thousands of contributors, which is where they are clearly steering the whole platform.
There is also an AI angle Epic was less loud about. Text-based code is something LLMs can read, write, and assist with. Node graphs are not. As AI tooling becomes part of the pipeline, a text language is a much better fit. Read into that what you want.
The community reaction
It has been loud. A Change.org petition to keep Blueprints appeared within days. The forums lit up. The core fear is real: Blueprints were the on-ramp that let non-programmers make games, and replacing them with a programming language raises the barrier.
Epic's answer is that Verse will eventually get a visual scripting layer on top of it, a Blueprint equivalent built on the new foundation. But that interface does not exist yet, and "eventually" is doing a lot of work in that sentence.
What this means for you
If you are shipping on UE5 right now: keep going. Finish your project. Do not panic-port anything. UE5.8 is supported and stable, and the migration tools are not even out yet.
If you are learning Unreal: this is the important part. The future of Unreal is code, not nodes. The shift to Verse confirms what serious Unreal developers already knew. Understanding actual programming, real C++ for engine-level work and now Verse for gameplay, is where the durable skill is. The people who only ever learned to wire Blueprints are the ones with the most to relearn.
If you are deciding what to invest your time in: learn the fundamentals that transfer. C++ teaches you how the machine works, which makes Verse (and any language) easier to pick up. Verse itself rewards people who understand programming concepts, not people who memorized one engine's node system.
This is the bet we made when we built Game Dev Junkies. We teach the deep foundation, real C++, the systems underneath, and the way games are actually built in code, because that is the skill that survives an engine changing its entire scripting model overnight. Blueprints getting deprecated did not surprise us. It is exactly why we never built the course around them.