Tim Sweeney says Unreal Engine 6 will drop Blueprints and the C++ Gameplay Framework

WHAT HAPPENED

For years, Blueprints have allowed Unreal developers to build game behavior by connecting visual nodes instead of writing traditional code.

Artists use them to make doors open. Designers use them to create combat encounters. Small teams use them to prototype entire games without needing a dedicated C++ programmer for every system.

Unreal Engine 6 is preparing to leave that approach behind.

During the November 3 Unreal Fest Tokyo keynote, Tim Sweeney outlined an accelerated transition away from three familiar Unreal systems: Blueprints, Actors and the C++ Gameplay Framework.

The announcement changes Epic's earlier plan.

In June, Epic said these systems would remain available in the initial UE6 releases and gradually be deprecated once their replacements were mature. The new plan, according to journalists attending the Tokyo presentation, calls for their removal beginning with UE6 Early Access, currently targeted for late 2027.

The replacement has two major parts.

Verse becomes the principal language for implementing gameplay. Epic has been developing Verse through Unreal Editor for Fortnite, where creators already use it to program interactive systems.

Scene Graph becomes the new framework for organizing scenes and gameplay objects. Instead of relying on traditional Actors, developers build with entities and components containing data and behavior.

There is an important distinction: Epic is not removing C++ from Unreal Engine entirely. The language remains part of lower-level systems such as rendering and physics. What Epic intends to remove is the traditional C++ Gameplay Framework.

Why Epic is making the change

Sweeney says Epic's internal experience with Verse, Scene Graph and AI-assisted development has convinced the company that the new approach can substantially improve productivity.

At Tokyo, he reported internal productivity improvements ranging from 1.5 to four times across programming, debugging and level-design work. Those figures are Epic's own measurements, not independently verified benchmarks.

The larger ambition is portability.

Epic wants content, gameplay systems and code to move more easily between Unreal projects, Fortnite experiences and other connected environments.

The company is also building AI into its development tools through technologies including Model Context Protocol and Python scripting interfaces.

That creates a workflow in which a developer can direct an AI assistant to create or modify gameplay systems, with Verse supplying the underlying programming model.

What happens to existing projects?

This is the difficult part.

Studios have invested years in Blueprint graphs, C++ gameplay systems and custom Actor-based tools. Rebuilding those systems manually would be a considerable undertaking.

Epic says it is developing AI-assisted conversion tools to help translate existing Blueprint and C++ gameplay logic into Verse. The exact capabilities, reliability and release schedule of those tools have not been established.

Sweeney acknowledged that losing Blueprints will be painful for developers and apologized during the presentation.

Epic is already working through the transition internally, moving Fortnite's existing gameplay systems toward the new architecture while keeping the live service running.

Developers with projects already in production on UE5 are not being forced to migrate immediately. Epic intends to continue the UE5 development line, including UE5.9, whose preview was announced for the week following the keynote.