Why do I need to choose a parent class when creating a Blueprint Macro Library?
Unlike functions, macros are only valid in certain scenarios. For example, “Retriggerable Delay” cannot be used in a Macro Library for an Object because latent actions require an actor. (I’m still new, but I think this is correct.)
It’s also useful to limit the use of your macro libraries to specific types to reduce the noise in your add action dialog. There’s no point polluting it in a Pawn with macros for Controllers.