Sat, 2022-04-16 13:57 — theblackswordsman Blueprints vs. C++: How They Fit Together and Why You Should Use Both Video of Blueprints vs. C++: How They Fit Together and Why You Should Use Both I forgot to add a description! 0 No votes yet
Comments
(Short Spike)
No.
I can say with 1000% certainty that I understand this engine better than anyone here.
(Old Spike)
What I'm curious about is many say you need to use both blue prints and C++ to some extent or another. Why can't you use C++ entirely if you choose?
The blueprints themselves were constructed from a combination of C++ and gui's, so why would it be impossible to do 100% code?
Or is it simply an exageration/simplification when one claims you "need" to use blueprints sometimes?
(Short Spike)
You don't 'need' blueprints.
You can use C++, blueprints, a combination of both or... *drumroll*. Whatever you want!
How? plugins. Instead of blueprints you can use lua, python, brainfuck, or whatever you want to use to handle the higher level ('scriptable') stuff.
Same goes with C++. There are ways to mess with the lower level stuff (Rust, Go, C or anything that compiles down to machine code).