Decoupled Event Channel Architecture Simulator

Click Broadcaster actions and observe independent listener responses

BROADCASTER (Player)

Player HP: 100 / 100

EVENT CHANNELS (Project Assets)

OnHealthChangedSO 2 Listeners

OnScoreChangedSO 2 Listeners

                    [Ready] Broadcaster initialized. Zero direct dependencies.
                

DECOUPLED LISTENERS

HealthBar UI Subscribed

SFX Manager Subscribed

Idle

Score Counter Subscribed

Score: 0 pts

How The Connection Works: Broadcaster calls RaiseEvent(val) → ScriptableObject executes _onEventRaised?.Invoke(val) → All registered listener methods receive that variable!

1. BROADCASTER

PlayerCombat.cs

// Broadcaster code

2. CHANNEL SO ASSET

IntEventChannelSO.cs

// Channel SO code

3. LISTENER RECEIVER

HealthBarUI.cs

// Listener code

LAB MODE STUDY GUIDE: DEEP DIVE

BREAKDOWN

Simple Analogy (The Core Concept):

Try clicking 'Take 25 Damage'. Notice how the Broadcaster fires ONE pulse into the Event Channel. Then, both the Health Bar and the SFX Manager update instantly! Now uncheck 'HealthBar UI' (simulating the UI being closed) and take damage again. Everything works without a single error!

What is What:

Event Bus: The central highway where event messages travel.
Dynamic Listeners: Listeners can join, leave, or be turned off at runtime without affecting the broadcaster.

Key Differences (X vs Y):

Fragile Direct Reference: If HealthBarUI is disabled, Player crashes with NullReferenceException.
Decoupled Event Bus: Player broadcasts happily whether there are 0, 1, or 20 listeners active.

Common Trap and Why It Breaks:

Assuming events are slow. In C#, a delegate invocation is a direct function pointer. Thousands of event calls happen in less than a single millisecond.

Golden Rule for Your Project: Test your broadcasters with zero listeners active in the scene. If they run cleanly with no errors, your architecture is solid.

HR Teacher Mode Access

Keyboard Shortcuts

Teacher Speaker Notes [N]