1. What This Toolkit Solves

Use this toolkit to build decoupled gameplay communication with low wiring friction:

1. EventBus (EventBus<T>) for global/system-level code-driven events.
2. Event Channels (EventChannel<T>, SignalEventChannel) for designer wiring in Inspector.
3. EventListener for channel-to-UnityEvent callback routing.
4. Animation Event Manager for clip-event-to-channel mapping using deterministic keys.

Quick module selection:

• Use EventBus when both producer and consumer are code and you want no asset references.
• Use EventChannel when designers need drag-drop references between scenes/prefabs/assets.
• Use Animation Event Manager when animation clips should trigger mapped signal events.

2. Project Map

Core runtime files:

• Assets/DEV505/EventSystem/Scripts/Runtime/EventBus/EventBus.cs
• Assets/DEV505/EventSystem/Scripts/Runtime/EventChannel/EventChannel.cs
• Assets/DEV505/EventSystem/Scripts/Runtime/EventListener/EventListener.cs
• Assets/DEV505/EventSystem/Scripts/Runtime/Animation/AnimationEventManager.cs

Useful demo scenes:

• Assets/DEV505/EventSystem/Demo/EventBus/Demo.unity
• Assets/DEV505/EventSystem/Demo/EventChannel/Demo.unity