[=;361140]
Disagree with all the BP hate in this topic… Blueprints are great. As a programmer your most precious commodity is usually time, and so long as the game runs at 60 FPS, who cares? Personally I can usually write code faster than I can Blueprint something now, but BP’s are second-to-none for fast prototyping and giving artists the ability to demonstrate what they want to do.
Blueprints are also a fantastic learning tool for C++ Programmers, because it helps we/us/them/they get familiar with the UE4 API much quicker. I wouldn’t be half as competent with C++ as I am now without having BP as a reference at times (hell it’s better than the docs sometimes). You can either have power and flexibility, or lack of both in favor of total simplicity.
A lot of these suggestions sound like they’re asking for a glorified ‘Make my Game’ button, with a few options to tweak the outcome. I really hate that attitude towards development, it shows no passion at all.
I’ve seen some say BP’s != programming? Over the years I’ve used tons of scripting / OOP type’s with game programming and it’s relatively all the same… In UE BP’s you have Enums, Switches, Arrays, Functions, Variables, getters / setters etc. All the stuff you use in game coding pretty much.
How’s that not programming? To respond to your …
I agree, it’s great to get used to the API / Instant feedback and see what Epic will let you get away with. It has plenty of great explanations as to what’s going on, much better than the stuff VS dumps on you…