Post

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.)

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.

Sorry, but it isn't. I've seen multiple implementations of visual scripting that just transpile into something like Lua, and even aside from my vague references... Blueprint already gets compiled into what is a pretty bog-standard scripting language virtual machine.

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.

0 reposts0 likes

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).

The more likely reason might instead be that LLMs are much smarter (or less dumb, though I'd say the first one) at making code that is written text than making a flowchart that is literally an image. In no small part because text is more efficient than inventing pixels.

I've heard this before and I don't buy it. This direction of verse replacing BP was set well before the current state of LLMs. Also, LLMs do not interact with BP as an image, BP has a textual representation. They're just worse with it because it is not similar to what they've been trained on.

I forgot to mention the other piece disproving this claim: verse itself was (and maybe still is?) originally running on top of the blueprint virtual machine!

To be clear, it's a good thing they moved/are moving off of it as the blueprint VM is slooooow. But clearly both languages can be compiled into representations that support all the features needed by the other, so the issue here isn't inherent issues with visual scripting but Epic's own priorities.