Pawn, Controller -- what's the third class?

[HateDread]

@jwatte;89664

Looking into this some more, it ends up being trouble anyway, because the controller should enforce rules (“no missile firing when out of missiles”) which means it has to grab a bunch of state from the pawn anyway, so there’s still some code duplication.
Some simple way of implementing delegation in blueprinting would go a long way towards solving this problem. (Note: interfaces express the possibility to delegate, but does not allow for elegant implementation of such delegation)

I’m not sure I see how my suggestion wouldn’t get around this issue. The event fires off when the controller (either player or AI) sends the ‘Fire Missile’ message. That can be received by the pawn, where your ammo logic can occur, or could call a FireMissile function on an owned ‘Launcher’ (if you broke it down to this point, I mean, for further decoupling, with a separate BP/class for the weapons/launchers), which itself would decide if it could actually fire.