Hey everyone,
This is my first time posting here, so I hope I’m doing it right! I’ve recently started learning Unreal Engine and… wow. It’s amazing, but also kind of overwhelming at times. There’s just so much to learn, and I’m still figuring out where to even start.
Right now I’m mostly exploring Blueprints, just trying to make simple things work like basic movement, triggers, and maybe some interactions. I have no background in programming, so Blueprints have been a lifesaver. Super powerful once you get the logic down (still working on that part).
What’s surprised me the most so far is how satisfying it feels when something finally works after hours of trial and error. I know it’s small stuff — like making a light turn on when I enter a room — but it’s still a win!
I’ve been watching YouTube tutorials, reading docs, and lurking on this forum a lot. Honestly, the Unreal community seems really cool, and it’s helped me stay motivated when things get frustrating. Just wanted to say thanks for that.
If anyone has tips for absolute beginners — especially around organizing Blueprints or understanding how actors communicate — I’d love any advice.
Looking forward to learning more and maybe helping others in the future when I (hopefully) know what I’m doing 
Cheers,
Hey @Aliibabu899 how are you?
Welcome to the game development world! You’ve already taken the most important step: getting started! Now you just need patience and a thirst for learning new things.
Here are some tips based on my own experience:
Blueprints Organization
-
Use naming conventions: there are a lot of things you can do to keep your file names understandable, and the most important one is “naming conventions”. For example, “BP_” should be the prefix for all your blueprints in mosta cases, but you should use “WBP_” for widget blueprints, or “BPI_” for blueprint interfaces (Examples: “BP_PlayerCharacter,” “BPI_InteractableObject,” or “WBP_MainMenu”).
-
Create folders for each part of your game: into the “Player” folder you can save your BP_PlayerCharacter, its meshes and textures, its abilities, etc. You can do the same with “Enemies” folder to keep their art and abilities separated from those which are for the player. Then you can have a separate folder for “Levels”… I think you got the idea haha
-
Use a lot of comments: if you select a couple of nodes and then press the “C” key, you can group those nodes and add a comment about them! This is really usefull to remember what those nodes do after a long time without touching them
-
Last but not least, keep your blueprints focused on single responsibilities: each blueprint should have only one job, you should never have a massive blueprint that handles your abilities, inventory and UI all together! Be granular and create a BP for each ability, another BP for UI, a BP for each different enemy, etc.
One last advise
Begin with Epic’s templates rather than blank projects. The Third Person template, for example, gives you a working character controller to study and modify, which teaches you more than starting from scratch. The same applies for each other template! You will learn a lot just tinkering with them!
Hope this helps you to keep forward! Don’t hesitate to create a new post if you need help!
Hello, Welcome!
For your question on “understanding how actors communicate” - I’d give this legendary tutorial a watch.
As far as posting in the right spot - I’ve moved this from ‘Programing & Scripting - C++’ to ‘Programing & Scripting - Blueprints’ since it sounds like you are BP focused - I’ve also removed the fortnite related tags since it does not sound like you are using UEFN.
+1 for the feeling of satisfaction when you get something working after banging head against keyboard for a few hrs 
1 Like