Hi, I’m new to UE5 and already following some courses but, in the meantime, I’m searching quality of life advice with Blueprint like organizing your work or where to load something, etc; something that you may discover along the road and say “If only I have known that before…” or something that will make you change completely your approach to UE5 or go back and change everything you have done.
Just to clarify I’ll put some minor examples that I have found:
Game Instance is good to load “Global Variable” cause is always loaded and accessible from every Actor or Blueprint
Use just a few Global Variable or not at all
…
Obviously I’ve searched something similar online but I’ve found nothing so far.
Well, thanks for everyone who want to give it’s 2 cents
I recommend learning how to use Blueprint Interfaces, and Event Dispatchers, and why casting is bad. These are very performant, and will probably be used in almost any type of game you make. You will see a LOT of new to Unreal Engine tutorials out there that do NOT use these, and they are bad, but get the job done, like Matt Aspland, and Gorka Games.
Learning good practices at the start, and why they are good practices, I think would be the best advice I can give you. 4 channels I recommend that do a good job of not just showing you what to do, but WHY something they do is the better way, are:
Ali is my favorite channel, he’ll help you understand how to do things properly, and usually responds to YT comments asking for help, and has a good discord community.
LeafBranchGames is very smart and technical, and is where I learned that using Event Dispatchers is much better than binding a variable for a progress bar in a UI for a health bar.
PitchforkAcademy has a lot of good tutorials that also use good practices, highly recommend checking them out.
Ryan Laley is probably the most popular, but he does like 12 tutorial series at once, and it takes forever for him to finish one. He is very good at explaining stuff so it’s easy to understand though, even if he has a lot of bugs in his tutorials.
The child actor component is a real evil, especially in a multiplayer game.
Replication and ownership - sometimes behaves randomly weird and you literally can’t figure out why your code doesn’t work until you add Print String EVERYWHERE to make sense of it.
And so you launch it to check - and the problem disappears by itself…
