This will be one hell of a transition for everyone that prefers to work with Blueprint over code, like me.
So, what do we think about this?
I personally would prefer to use SceneGraph+Blueprint over SceneGraph+Verse, since I am already doing the very same thing that SceneGraph will implement anyway, within current limitations of course.
At least give us a visual way to code Verse, as replacement for Blueprint?
I really gave it a go and spent around 2 weeks in UEFN trying to learn it, and it was genuinely one of the most apalling experiences in the last 15 years of game dev (just behind trying to recompile code for Mac)
I’ve spent the last 10 years learning blueprints, and now they’re throwing it away so we have the “opportunity” to publish on fortnite? Yeah that seems a little crappy to everybody but high level executives.
Would immediately trade Blueprint for that functionality, since I dont care about Fortnite, not even remotely.
I mean… I can always just stick with UE5 or early versions of UE6 - but if Blueprint is already in early versions of UE6, as they announced, then why remove it?
Realistically right now the UE indie development ecosystem is being propped up by over a decade of material from as far back as UE4. Right now they are proposing basically throwing this away.
“You’ll be able to ship directly in Fortnite”
I have zero desire for this. Serious developers are not looking for a Roblox alternative.
“while we aren’t currently planning another official UE5 release after 5.8”
This is quite alarming. UE5 is not finished. The 5.8 preview still has major issues and the experimental PVE is not done.
We’re moving the gameplay programmingmodel to Verse
Overall very depressing update. I think if Blueprint goes away and they double-down on Fortnite and Verse, it will be time for serious devs to move to another engine. I guess we’ll see, but a full transition to C#/C++ makes more sense to me than learning Verse.
Its even worse - this would mean a “clear cut” between 4/5 and 6, effectively making a decade of tutorials useless for anyone trying to learn UE6.
In the past you could use UE4 tutorials for UE5 just fine, with some adaptions because a button might have moved a bit etc. - this will be impossible for UE6, its all back to zero.
The current fortnite tutorials probably also wont cover the reality of a 2028 UE6 with all the features that probably never were exposed to UEFN for a variety of reasons.
============
This throws back the entire “Unreal Engine Ecosystem” back by, at least half a decade if we assume that early ue4 stuff isnt valid today anymore.
The one thing that UE excelled on: that you could just look stuff up on youtube → gone.
I mean… I will figure out, but any newcomer… very hostile environment for a few years.
We’re building development pipeline features such as an MCP with integrations for Claude, Gemini, and others, as creativity and productivity multipliers
It’s not AI slop, it’s a creativity multiplier
Blueprints was THE reason why i got into this engine instead of other engines… This will definitely eliminate a lot of newcomers… Really sad that they are going down this route instead of making blueprints better especially since I still, after all this years, think blueprints is better than c++ for lots of reasons…
^^ Yes exactly. It is a good on-ramp for newcomers.
For me, a shift to only C++ would make more sense than learning Verse. If I am faced with either switching to Verse or C#/C++, I am not sure why I would learn their special proprietary metaverse language when these other languages are more transferable skills.
