Blueprints Should Remain a Core Part of Unreal Engine's Future

Hello everyone,

I would like to start a respectful discussion about the future of Blueprints in Unreal Engine.

Like many developers, I have recently seen discussions about Verse, Scene Graph, and the long-term direction of Unreal Engine. While I understand that Epic Games wants to innovate and improve the engine, I believe it is important to communicate how valuable Blueprints are to a large part of the Unreal community.

First of all, this is not an anti-Verse post.

New technologies, better workflows, and new programming options are always welcome. If Verse can improve development workflows and open new possibilities, that is a good thing. However, many developers are concerned that Blueprints may eventually be replaced, deprecated, or pushed into a secondary role.

For many of us, Blueprints are not just a feature. They are one of the main reasons we chose Unreal Engine in the first place.

Blueprints have allowed:

  • Artists to become game developers.
  • Designers to prototype ideas quickly.
  • Hobbyists to learn game development.
  • Solo developers to build complete games.
  • Small teams to work efficiently without large programming departments.

Blueprints lowered the barrier to entry for Unreal Engine and helped create one of the most diverse and creative communities in game development.

Many successful projects, prototypes, indie games, educational projects, and even commercial releases have been built with Blueprints. Their value goes far beyond simply being a visual scripting tool.

One of the biggest strengths of Unreal Engine has always been freedom of choice.

Developers can choose:

  • C++
  • Blueprints
  • A combination of both

This flexibility is one of Unreal’s greatest advantages.

I believe the future should continue to embrace that philosophy.

Verse can be an excellent addition to Unreal Engine. Developers who prefer text-based scripting should absolutely have that option. However, visual scripting should remain equally important and continue receiving support, improvements, and long-term commitment from Epic Games.

Not every developer wants to write code.

Not every developer enjoys writing code.

And not every developer should be forced to change their workflow if their current workflow is successful.

Many solo developers and indie developers have invested years into learning Blueprints. Some have built entire businesses, projects, and careers around Unreal Engine’s visual scripting ecosystem. Naturally, discussions about a future without Blueprints create uncertainty and concern.

My hope is that Epic Games continues to support Blueprints as a first-class development tool for the foreseeable future, even as Verse evolves and becomes more powerful.

Innovation does not have to come at the cost of accessibility.

Verse and Blueprints can coexist.

Developers should have the freedom to choose the workflow that best fits their skills, goals, and projects.

For those who feel similarly, I have created a community petition:

Whether you agree or disagree, I would be interested in hearing how other developers feel about the future of Blueprints and Unreal Engine.

Thank you for reading.