What about when there are multiple different types of actions (applying damage, applying debuffs, stunning, pushing, teleporting, etc.) that you want to mix and match with different targeting? Then the inheritance tree quickly breaks down and becomes unmanageable.
applying damage) explicitly in the derived class. In that example code, each ability defines its actions (e.g. This seems like a horrible idea that does not extend well at all. Instead of defining modular components, like different targeting types, that can be plugged into abilities freely, that tutorial creates an inheritance hierarchy, with a base Ability class and each type of targeting being a separate derived class.
SKILL INHERITANCE TOOL HOW TO
For example, this is an official Unity tutorial on how to create abilities using ScriptableObjects: The Unity tool best suited for an ability system seems to be ScriptableObjects. However, Unity does not have tools to create a system with nested components that can be modified in the editor. You define an event block, and then define the various actions that will occur on that event. Here's the fundamental problem: a proper ability system will build abilities out of modular components like targeting, effects, etc.įor example, take a look at DotA 2's ability system: Ībilities are built with nested components like modifiers, events,and actions.
I've been researching all the resources I could find on implementing ability/skill systems in Unity, and I've come to the conclusion that there's no way to properly design and implement one using Unity tools.
0 kommentar(er)
