Cyclical dependency issues still in 4.9

[John_Alcatraz]

@CriErr;384165

Question is, isn’t that too many childs and references?
And what exactly is a reference, issue coming from, casting?
Because when im checking my spell system actor, which handle everything, from animations to widgets it has references everything to interface and than to actual blueprints and only two widgets which has casting, reference blueprint to blueprint.
Mb that’s an idea, for hardly dependent stuff, to use interfaces?
I’m not criticizing, i’m asking.

I’m not sure I can get your point. You think I am using too many references and ask me why I am not using interfaces? Your English is a bit hard to understand. I can’t use interfaces for everything like spawning actors and so on. But once I spawn an Actor from a widget the actor is referenced, the actor is referencing the player controller, the player controller is referencing all kind of stuff like Gamemode and all kind of managers I have created and so on.