I am beginner. is it better to make own blueprints to learn or use Asset controller for FPS game? Would not it be harder to understand Asset if you dont know nodes etc when u make them yourself
In my opinion, I’d recommend starting from scratch before examining others’ solutions. This approach encourages you to actively engage with the “what” and “why” of the programming concepts yourself. Once you hit a bottleneck or aren’t sure how to proceed, then look at how others have solved similar problems. You might be surprised to find that their solutions aren’t always perfect, which is a valuable lesson in critical thinking.
As for Blueprint nodes, they are quite intuitive: simply right-click in the graph, search for what you need (like “Get Actor Location”), and you’ll likely find the relevant node.
Hello @User-b9cc7537bf ,
If your main goal is to learn, I recommend starting by creating everything from scratch with your own Blueprints. It’s not an easy path, but when you build your own systems, you not only learn what each node does, but also why you place it there. This helps you understand the logic behind gameplay and develop problem-solving skills, which are essential for creating games. Over time, that understanding becomes one of your most valuable tools as a designer or programmer.
If you start directly with a complex asset, you’ll be using functions that “just work,” but without understanding how or why. That can make you dependent on the asset and limit your ability to modify it deeply. Creating your own systems from scratch is a long-term investment, because if one day you want to change something, you’ll already know where to look and how to fix it.
A practical tip: start with something very simple. For example, a player that can move, a first-person camera, and an input that prints text on the screen. Don’t try to create the perfect weapon on the first day. What really matters is understanding the basics and moving forward step by step.
That said, FPS controllers and other assets are still very useful as references. A good way to use them is to open them once you already have your own base and compare: observe how they solve the same problems you did, how they structure events, and how they organize variables. Then you can ask yourself questions like why did they do it this way? why did they use this specific node? or is their logic cleaner or more efficient than mine? That kind of analysis teaches you good practices and helps you understand the reasoning behind each system, which in turn improves your own project.
I also recommend visiting the official Unreal Learning site.
It’s the best place to start learning the fundamental concepts, with examples, community references, and materials from Epic’s own developers.
In summary, building your own Blueprints teaches you to understand; studying the logic of an asset teaches you to improve.
And don’t hesitate to use the forum whenever you have questions. There’s always someone willing to help when something isn’t clear.
Hope it helps!
Thanks, thats what I thought. Use right now or have ability to change complicated game mechanics later and know how to do it.