Blueprints are a toy. Which serious Unity dev would use UE4 without C#/F# or UnrealScript!?

[SchnitzelDude]

@CriErr;578595

As a person, who been working with unreal blueprints for a year now and have quite a big pure blueprint project (200+ blueprints, thousands of functions) i have to admit, pure blueprints are absolute trash developing on,there are way too many basic things missing, dozen things which one engineer from epic could implement in like a a month and make blueprints much better, but epic not willing to spend resources on optimizing blueprint workflow and add features purely for this, because epic use c++ as a core in their projects and this made them to avoid most of the issues which comes with complex blueprint project.

I don’t see why “pure” Blueprints should be trash. I’m developing a whole game using only Blueprints. It’s like a proof of concept and currently it’s doing really well. We are going to ship our project in the near future and we never had problems with Blueprints. As a programmer you should have learned to find workarounds for minor missing things.