Yea but why are you creating flow charts? Because it’s an easy way to visualize the solution for a complex problem. It’s a good way to keep your logic clean. After a software architect created the flow chart the programmer just needs to write it down. Using blueprints you are the architect, who designs a solution for a specific problem. After you’ve finished your flow chart “Blueprint”, the engine does the code writing for you.
I don’t see why Blueprints should be more spaghetti than C++.
[/QUOTE]
True, flow charts are clean. But flow charts, at least in that image above, they don’t have variable pins. They only have execution pins that lead from one node to another. And that’s where the spaghetti can get out of hand. If you have to use lots of variables, there is going to be a lot of pin wires. Such an algorithm is then better left to C++. I Just thought that BP nodes could do more than this. ![]()
So, it’s just prefabrication, some data storage, some programming (or more if you are a noob), and passing it all on to C++ with shorter than C++ compile times.