Trending: Silksong patch 4Search
iHeartGeek
iGaming

Unreal Engine 6 drops Blueprints in favour of AI-assisted conversion

Epic says Unreal Engine 6 will move from Blueprints to Verse and Scene Graph, with AI-assisted conversion expected to help developers migrate existing projects.

A computer monitor displaying source code beside a laptop, illustrating game-development scripting

Epic Games says Unreal Engine 6 will drop Blueprints and the Actor Gameplay Framework before launch, moving new gameplay work towards Verse and the Scene Graph framework. The change arrives earlier than the company previously indicated, with Epic arguing that AI-assisted conversion can help existing Unreal Engine 5 projects make the jump.1

What Epic is changing

The announcement, written by Epic executive vice-president of development Marcus Wassmer, says Unreal Engine 6 — including its Early Access release — will not include Blueprints or the Actor Gameplay Framework. Instead, gameplay will be built in Verse alongside the new Scene Graph framework.1

That is a significant change for developers who have built projects around Blueprints, Unreal's visual scripting system. Epic had previously said Blueprints and Actors would coexist in Unreal Engine 6 Early Access and version 6.0, giving Unreal Engine 5 projects a more gradual upgrade path while Scene Graph matured. Wassmer's new explanation is that recent advances in AI could help convert those projects, potentially automating much of the work.1

Why the decision matters

Blueprints are more than a convenience feature. They give designers and artists a way to build and test gameplay logic without writing every system in traditional code. That makes them an important bridge between creative and engineering work, particularly on teams where not every designer is a programmer.

Epic says Blueprints will not be deprecated in Unreal Engine 5, so existing projects are not being abandoned in the current engine. The company also says its team has been converting Fortnite's Blueprint library to Verse with AI assistance, and that this work has helped support the new timetable.1

The open question is whether an automated conversion can preserve the intent and the maintainability of a large project. Translating nodes into another language is one task; checking edge cases, performance, debugging behaviour and the assumptions made by the original designers is another. Developers may welcome faster migration, but they will still need a way to inspect and trust the result.

Our opinion

Epic's decision makes Unreal Engine 6 feel like a bet on the workflow around AI, not merely a change of scripting language. Verse and Scene Graph may produce a cleaner long-term foundation, but removing a familiar visual tool raises the cost of entry for the people who used it to learn how games work.

The strongest version of this plan would make AI conversion an assistant rather than a black box: show developers what changed, preserve a readable migration trail and let teams validate each system before it reaches production. If Epic can do that, the transition may be manageable. If it cannot, the promise of automatic conversion will not replace the practical safety net that Blueprints provided.

For now, Unreal Engine 5 developers can continue using Blueprints. The impact will come when Unreal Engine 6 Early Access arrives and teams can test how much of their existing work can really make the move to Verse and Scene Graph.