BP main game logic best practice
Is there a best practice in terms of where you put your BP game logics?
Like do you use the Level BP / GameState / BP in game world ?
I'm kind of lost in the world of blueprints for me the thing looks a bit disorganized compared to my previous scripting experiences where the code has a main entry point.
asked May 04 '15 at 06:36 PM in Blueprint Scripting
The PlayerController or PlayerCharacter if you don't use a Controller is the heart of all the Gameplay Blueprints, and C++ that I have done. Since everything is based off the Player's interaction it makes the most sense.
If you want to access something in a MainEvent loop, enable tick on your actors, and pull off from the tick event.
Blueprints are as organized as you make them. Through folder structure, interfaces and hierarchy, as well as decomposing into functions and keeping the main EventGraph sparse and just to handle events you can have very large and organized projects.
answered May 04 '15 at 06:46 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here