Post

did a blog post of my Thoughts on the Actual State of Unreal in 2026, how it has come to this, etc etc. i've been an unreal user since 2008, and this is the worst the vibes have ever been. is there hope? perhaps www.joewintergreen.com/absolute-sta...

Good stuff! Some personal opinions: 1) IMO removing Blueprints isn't bad per se. There are great advantages to moving back to a pure text scripting language. But what sucks is that Verse is designed around crazy bullshit metaverse concepts which won't fit AAA gamedev or other customers (film, etc.)

Hard disagree, there are no advantages to getting rid of Blueprint. Adding a text language *as well* would be fine, lots of teams use the Angelscript branch for that

Of course there are no advantages to getting rid of it. But I'm sure that's what people also said when UE4 killed most of UE3's scripting tech. The difference is that UE4's Blueprints were arguably better, and so it turned out OK.

I don't think most people did say that. Unrealscript was very cool imo, I think it's sort of a shame Blueprint wasn't basically a visual layer on top of Unrealscript. That's where they shoulda gone instead of Verse

I suspect it's actually quite hard to make something that works simultaneously well in text and visual form. It probably requires being designed that way from scratch, and can't be "added on top". Happy to be proven wrong with examples though.

I’m not talking about a transpiler — that is indeed easy. I’m talking about a thing where you can switch between graph and text freely on the same script. It’s much easier indeed if you have to choose one or the other, and can only convert from graph to code once and not the other way.

Neither blueprint nor kismet could do that, though, so I'm not sure why that's relevant. They're not rejecting making an interface that can bounce between visual/text, they're rejecting even doing a visual-only layer on top.

Oh, sorry - I misinterpreted what you were responding to in Joe's post, I get what you're saying now. My bad!

Epic themselves have made a transpiler for it too! Blueprint nativization transpiled from the node-graph representation into C++. It sucked, because the method they used didn't get the perf benefits necessary to justify the maintenance cost, but it worked.

A friend of mine has also built a different transpiler for it that worked directly from the blueprint opcodes instead of the node graph, and my understanding is that worked even better. Regardless, it is not a particularly high technical hurdle.

It's pretty clear that blueprint just doesn't fit into Epic's vision of the metaverse, probably because it is hyper-specific to unreal and can't easily be broken apart from that (and they don't want to put the effort in to make a new scripting system on top of verse).