For years, Blueprints have been one of Unreal Engine's most accessible ways to build gameplay. With Unreal Engine 6, Epic is moving toward a different architecture—and the latest reports suggest the transition may be more immediate than originally announced.
What Epic originally announced in June 2026
In its official UE6 roadmap, Epic said Actors and Blueprints would remain available in early versions of UE6. The plan was to deprecate them later, once the Verse and Scene Graph framework was sufficiently mature, with conversion tools to help developers migrate existing projects.
What changed at Unreal Fest Tokyo?
Reporting from the November 3, 2026 Unreal Fest Tokyo keynote describes a revised approach: the legacy Blueprint and Actor gameplay framework, along with the existing C++ gameplay framework, would be removed from the start of UE6 Early Access. This differs from Epic's June written announcement. At the time of writing, developers should treat the Tokyo keynote reporting as a significant update while awaiting detailed official migration documentation.
Does this mean C++ disappears?
No. The reported change concerns the existing C++ gameplay framework, not all C++ support. Lower-level engine development, including areas such as rendering and physics, remains a different concern from the proposed Verse-based gameplay model.
What replaces Blueprints?
Epic is building a new gameplay framework around Verse and Scene Graph. Verse is designed for persistent, scalable game logic and uses transactional semantics. Scene Graph supplies an entity-and-component-style foundation. The final day-to-day editing experience and feature parity with Blueprint workflows still require more public detail.
What happens to existing UE5 projects and plugins?
Existing UE5 projects do not suddenly stop working because UE6 is in development. Continue using supported UE5 versions for production. Plugins that extend the Blueprint graph or depend on Actor gameplay APIs may need substantial updates or a different integration approach for UE6. No developer should promise compatibility before testing against a supported release.
What should developers do now?
- Keep production projects on stable, supported UE5 versions.
- Maintain source control and tested backups.
- Track Epic's official migration tooling and Verse documentation.
- Audit critical Blueprint- and Actor-dependent systems before planning a UE6 port.
- Avoid rushing to rewrite working projects based on preliminary information.
Bottom line: Blueprint developers have reason to pay close attention, but there is no need to abandon working UE5 projects today.
November coverage: GameMakers' Unreal Fest Tokyo report; Press Continue's English-language summary.
Sources: Epic Games: The road to Unreal Engine 6 (June 22, 2026); Epic Games: Unreal Fest Chicago.
Related: Read the UE6 roadmap overview. For current UE5 projects, see ForgeWireX Blueprint editor customization; UE6 compatibility is not currently claimed.