Honestly this makes way more sense to me than what they were planning on doing before. A major version upgrade is the perfect place for this sort of huge architectural change to happen without concerning yourself with supporting existing content/code (of certain types). The previous plan felt like a trap that would make the initial migration easy and then lock those developers in to all the future UE6 updates. Now it’ll be much clearer that if you want blueprint/actors, you just stay on UE5.
None of that is to say that I agree with this whole plan to remove Blueprint. Only that given the stated goal of removing it in UE6, removing it immediately makes more sense than deprecating it initially and then eventually removing it at an indeterminate time in the future.
so everything on Fab outside of core engine plugins touching rendering, and pipeline and models/textures will need to be fully ported, and in several instances be completely useless.
Great “creator economy” for people making gameplay systems. I hope Tims investment into Anthropic pans out.
All I am seeing is taking a functioning engine fully founded on C++ a highly professionally portable language, and Blueprints which many engines have been trying to duplicate, if not fully founded on.
Then turn it into a “proprietary” and “in house” language of Verse which is unless Sweney convinces a bunch of other companies to use his language is far less professionally portable. A newer dev can’t take their Unreal Verse programming experience and go over to finance, but they can be an interchangeable vibe-coding seat warmer at an Unreal focused game studio.
This is worse then when Unity induced “Boo” as “the future language of Unity going forward…” they at least had the foresight not to remove C#. The biggest difference is that so far we will still be able to touch the C++ core engine.
This is an abysmal decision. Blueprints provides a visual way of crafting game logic which a lot of indies AND professionals use. Create code, expose to BP and reuse systems.
I think overall this is a very bad business decision from Epic.
Wow that are really bad news… blueprints was the reason, why i started with unreal. I think that’s exactly what makes unreal special, and now they are planning to get rid of the very thing that sets it apart? Holy ■■■■, i cant believe that..
When Blueprint goes, so will many developers.
Most will stay on UE5 until someone makes a fully visual Verse plugin or application, or someone finds a way to bring Blueprint back.
As for removing C++, that will likely prevent many studios from upgrading at first.
This AI conversion tool can’t be 99% correct. It needs to be 100% accurate, which is something AI has consistently proven to be impossible. The AI tool would also need to be able to translate third-party plugins.
Converting C++ might work, but some Blueprints will be almost impossible to convert accurately.
If Epic were smart, they would create a visual Verse editor that generates Verse code in real time while we work with a node-based system. That would make learning Verse much easier.
One last thing: with Verse coding, what happens if developers don’t fully understand how the code works and a security vulnerability appears? What if a single bug creates a backdoor that affects all games built with it? Blueprint had certain safeguards against that, while C++ did not.
So, instead of getting rid of ancient code within the Source Code, fixing Editor performance issues and crashes, and empowering heavy Blueprint users with C++ - which, by the way, they mentioned in a talk that I unfortunately do not have access right now, that they wanted to try and combine both C++ / Blueprints to empower each other, and you wouldn’t have to know how to code to get the full benefits of C++ - they are… doing this.
Removing the ability for anyone to type a single paragraph of C++ for extended capabilities of your own project, and removing the so learned and loved Blueprints from people who don’t know how to code, but still have the creative and logical capacity to build games.
If Epic isn’t cooked after UE6, then there’s no hope for the gaming industry, because this will mean that people don’t care, don’t mind, and we’ll enter a new dawn of game development that I don’t know if I want to take part in.
Since Epic Games is deep diving so much into AI, then I hope thousands of UE clones start popping up left and right, that still support the C++/Blueprints framework. You can be 100% sure I’m hopping onto whichever one is the most stable and completely abandon the official UE.