Provide a zero-allocation global event bus for Unity games.
npx skills add https://github.com/paek678/BuildUp --skill event-bus-system-paek678
Please help me install this Agent Skill. Skill: event-bus-system Source: https://github.com/paek678/BuildUp/tree/main/skills/01-architecture/event-bus-system Command: npx skills add https://github.com/paek678/BuildUp --skill event-bus-system-paek678
Decoupled global event bus enabling cross-system communication with zero-allocation events to minimize GC spikes during gameplay.
Define your events as structs implementing IEvent, publish with EventBus.Publish, and subscribe in OnEnable using EventBus.Subscribe, then unsubscribe in OnDisable.
High-intent search queries and answers about installing and using this skill.
To set up a zero-allocation event bus in Unity, define your events as structs implementing the IEvent marker interface, then use the static EventBus class to publish and subscribe. This prevents GC spikes during gameplay.
A publish-subscribe pattern enables decoupled cross-system communication by allowing gameplay systems to broadcast and react to events without direct references. The EventBus handles routing, ensuring subsystems remain independent.
The best way to manage event listener lifecycles is using EventListenerBase<T>. Subscribe to the EventBus during OnEnable and unsubscribe during OnDisable to safely handle listener creation and cleanup.
Yes, you can use struct-based events for type-safe messaging. By implementing the IEvent marker interface on structs, UI, gameplay, and analytics systems can safely publish and subscribe to strongly typed messages.
Garbage collection spikes during event broadcasting happen when events are allocated as classes rather than structs. Implementing events as structs with a zero-allocation event bus eliminates this memory overhead.
No, you do not need direct object references to trigger analytics events. A global event bus allows gameplay systems to publish events that analytics subsystems listen to independently without direct references.
MonumentalSystemsDesign Unity gameplay code with lifecycle-aware architecture and performance-safe patterns.
XeldarAlzCoordinate Unity systems with decoupled publisher-subscriber event channels.
OmerZeyveliOrganize Unity gameplay behavior into typed finite state machines.
8DionysusRefactor core modules by extracting concrete dependencies into narrow ports and adapters.
