[=;206345]
I like the blueprints system, I currenty use it. I did some C++ years ago and im perfectly fine with it and im not a bit against it.
Let’s make it easier: if there were 2 choices for scripting (just scripting, not programming) and those choices were blueprints and C#, and you don’t know either of them, what you would go for?
I think that would choose C# for the reasons states above (takes the same to learn both blueprints and C# if we use it only for scripting, blueprints knowledge is useless outside of UE4, C# is far more productive).
Once again, I’m NOT suggesting to remove C++, im suggesting to replace blueprints with C#
[/]
I understand your point, I would also like to see more scripting languages added, but as Dissonancient noted it should be done through the built in scripting support. way we can choose between languages and not force C# on those who are against it.
There is no need to remove blueprints, they allow to create gameplay. Text based languages as easy as they may seem to you and me are not going to be used by the vast majority of artists and level designers. Beyond that they are extremely useful when used together with code (as mentioned previously), and save a lot of for prototyping. I (and almost else here) would be extremely upset if they were replaced with a text based language, it is a step backwards to do so. I would fight to the bitter end to keep them if it was ever to come to that, thankfully it won’t.
Also:
[]
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.
[/]
Read through any thread on mono here on the forums, you will find plenty who had major problems with it.