[=;206534]
I just can’t see the point of blueprints, it is exactly the same thing as writing code, with less and more confusion. You declare variable, use get/set, call functions/events, pass parameters, where is the difference?
if you simply add some “decoration” to your code, like changing font and add some background color you will get the same thing! The only difference is that there is no point in learning it.
btw I choosed C# for the benefits I posted earlier, of course javascript/python/java or whatever language you want would be better than blueprints.
Nobody had any problem with unity C# and that’s a really old version of it, so you can’t say that designers are scared of it. Infact they won’t move from unity cause they don’t know either C++ or blueprints.
And you can’t say that “you can quickly test with blueprints” cause even the plugin for UE4 showed that you can have near-istant build.
it is not about “favorite language” but the best language for your goals, and not every languages have same the same features. @ since you are a .NET developer wouldn’t you like to be able to use LINQ and Tasks?
[/]
You really starting to sound like C# fanboy 
Maybe video will help you understand sense of blueprint:
https://.com/watch?v=ZxrcwNGnXZc