Video summary

Unreal Engine - The End of an Era - Blueprints & Actors Going Away?!?!

Main summary

Key takeaways

Technology

Key tech/product changes discussed (Unreal Engine 6 roadmap)

UE5/UEFN merge into one editor (convergence path)

Epic’s plan is to merge Unreal Engine 5 (standalone/high-end content development) with UEFN/Fortnite editor (live environment) into one editor.

  • Goal: studios can ship “traditional games” similarly to today, with options to:
    • ship directly in Fortnite, or
    • ship into their own ecosystem, optionally compatible with Epic’s ecosystem.
  • Transition philosophy: avoid a hard break; provide a manageable path forward for UE5-based projects.

Timeline expectations

  • First previews of Unreal Engine 6 are expected around end of 2027, with time allocated before the full transition.

“Bombshells”: Actors and Blueprints moving toward deprecation

Early UE6 versions will still include

  • Actors
  • Blueprints

These are expected to remain for compatibility, with migration via conversion tools to move projects from the UE5 framework to the UE6 framework.

Deprecation plan

  • Actors and Blueprints are intended to be deprecated once the new framework becomes mature (notably Verse + Scene Graph).

Blueprint replacement: Verse (visual logic shifts away from Blueprints)

Verse becomes the new programming language

The claim is that Epic is replacing Blueprints as the primary/general gameplay logic workflow with Verse.

  • Given rationale: Blueprints are considered difficult to make highly concurrent/safe, with a specific concern that they may be locked to a single thread, limiting performance/scalability.
  • Verse aims to enable:
    • Parallelism across cores
    • programming concepts friendly to atomicity/rollback/distributed processes
    • scalable, hyper-parallel execution

Blueprints don’t fully disappear

While Blueprints-as-game-logic are expected to fade, node-graph workflows are said to remain for other areas, such as:

  • Materials (node model similar to the Blueprint programming model)
  • Procedural Content Generation (PCG) graphs (described as very similar to Blueprint graphs)

Key distinction: what’s being deprecated is Blueprints used to attach logic to actors/scenes, not all node-based authoring.

Actor replacement: shift to ECS-style Scene Graph

Actors described as an inheritance-heavy OOP model

Actors are criticized as being an inheritance-based model—described as “clunky” and compared to a “90s object-oriented inheritance graph.” The presenter argues that game development has broadly moved toward composition.

Scene Graph becomes the foundation of UE6

The Scene Graph is presented as an Entity Component System (ECS)-style framework, intended to support:

  • Prefab-style workflows
  • runtime composition
  • a component-based structure replacing actor inheritance

Verse Scene Graph framework specifics (from described presentations)

Full integration with Verse

Scene Graph is described as fully integrating with Verse by using Verse’s type system to represent the prefab data model.

  • Engine-authored assets become concrete Verse objects/types
  • These are described as having a statically validatable API

Compiler-driven validation

A cited example: if you change a parameter in a particle system, Verse tooling can determine where code/data must be updated to stay consistent.

Higher-level gameplay frameworks

Planned frameworks are mentioned for common gameplay systems like:

  • characters
  • weapons
  • vehicles

The broader vision includes sharing across games/ecosystems, such as acquiring a “car” from Fab delivering a working Verse module (not just meshes/animations).

Broader analysis/implications emphasized by the video

The discussion frames the shift as similar to Unity’s DOTS/data-oriented approach, moving toward scalable, parallel-friendly architectures.

Potential ecosystem cost highlighted:

  • Large compatibility break: existing code/Blueprint/actor assets may not work directly
  • Automatic porting tools will be critical, but success is uncertain
  • Risk of a “clean break” for assets on the asset store

Overall framing: the transition promises modern architecture benefits, but may impose significant migration and compatibility challenges.

Main speakers/sources (as named in the subtitles)

  • Mike — Game From Scratch (presenter/commentator)
  • Epic Games developers/presenters (unnamed in the subtitles), discussing:
    • “State of Unreal 2026”
    • Scene Graph and the Verse Scene Graph framework
  • Matias — explicitly named near the end

Original video