This would be nice. But if you’re going for text scripts then you shouldn’t invent a new scripting language… what about… C#? The problem with blue prints is that you really need a massive screen to be able to see anything at all. They’re not exactly compact. I mean to do Math.sqrt(xx+yy) in Blueprints would can take up a whole screen. (Yes they have little scripts for math expressions now). But personally I prefer the middle ground of a scripting language somewhere in between C++ and blueprints. Other options would be Javascript/Python/Lua. But I just happen to like C#.
A compromise would be that blueprints are created from a text box. What I mean is you type in “myFunction” and a myFunction blueprint is created. Then you type in “(” and it jumps to the first variable, then you type in “23” and it fills in that variable, then you type in “,” and it jumps to the next variable. I think you get what I mean. So that typing a script and creating a blueprint from the keyboard is virtually identical.
Or just make blueprints more compact so you can fit more on the screen while still being able to read them!
Maybe people don’t realise that for people trained in text programming, switching to a visual system is actually quite hard!