Short answer: you haven’t wasted your time. Your UE5 projects keep working, and Epic says UE5 projects can stay on UE5. UE6 Early Access is more than a year away. What you learned in Blueprints, such as events, components, variables and debugging, is the hard part of game programming, and it carries over to Verse. This month: keep shipping on UE5, spend an hour a week on Verse in UEFN, and keep your projects tidy.
First, what actually happened
At Unreal Fest Tokyo on November 3, Epic said UE6 will remove Blueprints, Actors and the C++ Gameplay Framework, and move gameplay to Verse and Scene Graph. Early Access is planned for the end of 2027. The full story is in our news summary.
It’s fine to be annoyed. Tim Sweeney himself called it a painful change and apologised. But here is what it does not mean.
Your UE5 games aren’t in danger
- Blueprints work in UE5 today and will keep working there.
- Epic says projects already in production on UE5 can continue on the UE5 line, and UE 5.9 is on its way.
- Engine versions don’t expire. Games still ship on UE4 today.
If your game is due in the next two years, nothing in your plan needs to change.
Your Blueprint skills carry over
A Blueprint graph is a program. You already think in the ideas that every game language uses:
| You know this in Blueprints | It’s still there in Verse and Scene Graph |
|---|---|
| Actors with components | Entities with components |
| Event BeginPlay | OnBegin on devices, OnBeginSimulation on components |
| Delay node | Sleep(Seconds) |
| Variables, Branch, ForEach | var, if, for |
| Event Dispatchers | Events you subscribe to |
| Print String | Print |
The hardest part of learning to code is learning to think in events, state and flow. Blueprint developers already do that. What’s new is typing it instead of wiring it.
AI makes this switch easier than any before it
Epic is betting on AI for the move. It plans AI-assisted tools to convert Blueprints to Verse and is opening the engine to models through MCP and Python. Even today, AI assistants can explain a Verse snippet line by line or turn a description of your Blueprint graph into a first draft.
The honest catch: models know little Verse yet. Sweeney said himself that current leading models saw little of it in training, and expects that to improve early next year. And you still need to understand the result well enough to test it, which your Blueprint experience helps with.
What to do this month
- Keep shipping on UE5. A finished game is worth more than a perfect engine choice.
- Spend an hour a week on Verse. Epic Games Japan’s advice was to try Verse and Scene Graph in UEFN first. Start with our Verse first steps.
- Keep your Blueprints tidy. Small functions, logic in components, data in Data Assets. Whatever the conversion tools look like, clean projects will be easier to move. See how to get a Blueprint project ready.
- Use plugins for heavy systems. A good plugin gives you complex features as Blueprint nodes, so you spend your time on your game, not on rebuilding systems.
- Don’t panic-rewrite everything in C++. The C++ Gameplay Framework is leaving UE6 too, so a C++ rewrite won’t carry your gameplay over. Learn C++ when it helps your UE5 game today.
FAQ
Should I stop learning Blueprints? No. If you’re on UE5, Blueprints are still the fastest way to build and learn the engine.
Will there be visual scripting in UE6? Nothing has been announced. Plan as if you’ll type Verse, and enjoy it if a visual option appears.
Is Verse hard? Epic says it should feel familiar to people who know Python or C#. Its new ideas, like functions that can fail, take some getting used to.
Related reading
Keep building in Blueprints on UE5. Our plugins are written in C++ and used from Blueprints. For example, MIDI Engine 4 PRO gives you MIDI playback, note highways and music-game templates, and VST Audio runs VST3 instruments and effects from Blueprints and MetaSounds. Each plugin lists its supported engine versions. Browse all our Unreal plugins.