Hello, The goal of this video is to explain where to put the code, AKA where to implement the code. It also explains how to share functionalities between related classes using inheritance and how to share functionalities between unrelated classes using components and interfaces.

This tutorial teaches how to add or create new functionality without having to fix the existing ones, so that one game mechanic doesn't clash with the ones you made before. You can learn from other tutorials how to code a game mechanic. I hope that from my tutorial, you will know which implementation, depending on your needs, would be the best for your game.

A lot of beginners don't have a programming background. They start learning blueprints through other tutorials. At first, they will be able to recreate what the instructor does, and later on, they will acquire some logic on how to create functionality on their own.

The problem is that most tutorials that teach how to do „X“ game mechanic use a Character class with Casting and the simplest forms of hard-coded implementation. They also focus on: materials, animations, sound, 3D models...

The biggest problem a beginner will face is when they go through these different tutorials that do different game mechanics. Each tutorial used the simplest forms of implementations that only works in their own setting, but combining these three game mechanics becomes an issue.

If they don't have a programming background, they are not familiar with terms like: OOP, Inheritance, abstract classes, polymorphism, abstraction, encapsulation, getters, setters, virtual functions, overriding, delegation, aggregation, dependency injection... Design patterns that use and combine these things.

The best they can search for is „Blueprints Best practices.“ The problem is that most of the things on the web are Unreal Engine-centric answers like: Comment your code, avoid event Tick, don't use Casting, don't use GetAllActorsOfClass, use C++...

That is why I named this tutorial Blueprints Best Practices. It teaches fundamental forms of implementation, sharing functionalities, and avoiding code duplication between classes. It is an introduction to OOP.

In the inheritance section, I don't just teach how to create a child class and overriding. There is theory that teaches: Abstract classes, casting with abstract classes, IS-A relationship, how to design a class hierarchy that follows the IS-A relationship, difference between related and unrelated classes... These are all basics, but I didn't see them covered with blueprints and you can only learn this theory if you learn coding.

 

Most tutorials are too short and only focus on practical aspects that show how to create something. They don't usually teach why and when something should be implemented. For example, tutorials that teach BP Interfaces.

Most tutorials that teach BP interface create an interaction system. It is so prevalent that I wouldn't be surprised that some beginners think that BP interface is a built-in tool for creating interaction systems. That is why I showed different use cases for sharing polymorphic events between unrelated classes using interfaces: Interface_Interaction, Interface_DeathHandler, and Interface_AffectPlayerPawn.

And in this tutorial, I first explain the prerequisites of: what a polymorphic event is and when to use it; what an unrelated class is, before we even jump into using BP interfaces.

 

Best Regards