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

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

0 reposts8 likes

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 mean, all compiled code is literally converted into other code. I doubt the machine literally follows the Blueprints images to run, so at some point there is a compilation, whether via interpreter or as a full compilation into the game code.

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.