I want to learn how to apply good OOP practices to Blueprint Scripting, doesn’t matter if it’s video or something else. I only need them to be clear about how to apply this to Blueprints.
Blueprints kind of force you down the OOP route.
You have classes and class inheritance for example, right out of the box.
I’d say if you avoid the level blueprint, you’re probably most of the way there.
Thank you for answering, and I get what you mean. What I want to know is how to do it efficiently.
For example, I remember hearing that you should avoid casting as much as possible and only use it if it is completely necessary because casting in great numbers is very detrimental for performance. That instead of casting, I should use other ways to reference what I want.
I also remember that the same guy said something (I don’t remember exactly) along the lines of, “You should keep every class only for themselves, and if you want something like a variable or a function from another class, you should use …” (Can’t remember the last part)
Basically, this kind of information is what I’m looking for.