Function Override vs Interface vs Event Dispatcher

[wilberolive]

@Dividual;404405

this way the button doesn’t need to know about the door and the door doesn’t need to know about the button. only the level blueprint would know both, and you could trigger the door with lots of other unrelated things, like after a bossfight is won, or whatever.

So if your level had 100 doors and 100 buttons, each opening one corresponding door, does that mean the level blueprint would have to have all 100 button dispatcher events on its event graph, with each one wiring up to the Open function of a door?

@Dividual;404405

the interface is useful when you can’t use normal inheritance. for example, let’s say you’re making one of those games where the E-key uses things in the world. you have a lever you can pull, and an NPC you can talk to. the lever might just inherit from Actor, while the NPC is a Character. Nowhere to inject you own “UseableThingy” class in the hierarchy, so you can use an interface instead.

Ok this is interesting. I will be facing this exact scenario. At the moment I have created an actor that can respond to pressing the E key. Then I just derive from that actor to get specific functionality for other actors. I completely forgot about the case of also interacting with an NPC. They of course will be a character and therefore cannot derive from my custom actor. So now I can see a valid case for interfaces if I’m understanding this correctly.