event-systems

You can decouple game logic systems in Unity by using event channels or a static EventBus, letting publishers and subscribers communicate indirectly without hard references, which keeps gameplay components independent and modular.

To prevent memory leaks in a C# Unity EventBus, always unsubscribe listeners when they are disabled or destroyed. This Skill provides memory-safety guidance to help avoid dangling references and leaks.

Yes, this event system supports ScriptableObject event channels for UI communication, letting you wire publishers to listeners across scenes without direct references, enabling responsive and decoupled UI workflows.

Yes, you can use standard C# events alongside UnityEvent in the same workflow. The system supports both patterns plus ScriptableObject channels and a static EventBus to coordinate cross-system communication flexibly.

Avoid using a static EventBus for game logic when strict memory management is required, as improper unsubscription causes leaks. For scoped interactions, ScriptableObject event channels offer a safer decoupling pattern.