The image above follows a card battle from its content to its runtime results. Create the cards, characters and encounter in Game Card Editor, then open their Behavior graphs to define what happens in battle. In Play Mode, Game Card Monitor shows the result of playing a card so you can trace it back to the rule that produced it.
Bind a scene HUD in the Inspector and let spawned enemies register their own callbacks when enabled. Both can reference the same typed event asset. Give each listener an owner so it is clear who configures it and when it is removed.
A persistent audio service needs to hear the level-start event after each scene change. Keep the service GameObject alive, give each level the same event asset, and register the service as a persistent listener. Remove its callback when the service shuts down.
If a door sometimes stays locked after the player picks up a key, first locate the configured sender and receiver in Event Finder. Then reproduce the issue with Game Event Monitor open to see where execution stops.
Check the lifetime of every listener and scheduled action attached to an event. Scene objects should remove their own callbacks when disabled, and callbacks that can raise another event should account for paths that lead back to the source.
A generated room can connect its pressure plate to a trap only after the layout is known. Register the connection after creating the room, store the returned handle on the room owner, and remove the connection when that room is discarded.
If a damage event changes health and refreshes the HUD, register both listeners in the same priority tier and give the data update higher priority. Use the listener execution stages to check the order when the event mixes Inspector actions with C# callbacks.
Give a bomb a fuse by scheduling its explosion with RaiseDelayed. Keep the returned ScheduleHandle so defusing can cancel that exact request. The same handle pattern also works for repeated effects such as poison ticks.
Start the death sound and particles from the same event. Use a Chain when respawn must wait for the screen fade and scene load. Connecting these patterns to the same source keeps each response tied to its timing requirement.
A player-death event can start sound and particles immediately, then begin an ordered respawn sequence. In FlowGraph, follow the connections from the source to see which events branch and which events wait for earlier steps.