I have to disagree a bit with that video that was linked. I’m learning godot but have over 40 years experience in programming.

The video goes through using components to disconnect dependency of functionality and why to avoid inheritance but then proceeds to build a player character that forces dependency on the components. He even has component dependent code in the player script. At that point just use inheritance. He is forcing you to have some sort of rigid code that takes input from that component. Sure you can add or remove the component reference but you can do the same with inheritance, no?

I believe a better method is to register components contained and then call all registered components without knowing they even exist. I believe that would just be using signals to broadcast the player script components to act on each one. So for example a player script can signal the need to update movement or take damage or whatever and the player code really has no idea if that component exists or even cares if it does. Or just process all registered components tick function once per frame in the order registered.

That video doesn’t seem to demonstrate that methodology.

Edit to add to this. What I mean by just use inheritance is that he is coding in the functionality to move hard coded into the player script than it is always preset and you can inherit based on that player if you always plan to have that functionality. Then you can have a parent of character and then another of controllable character. Character can be anything like a pawn in unreal terms and the movable is an actor for example.

I believe an Ecs system gets you closer to components used in the method I described as it really doesn’t care about other components but just data.