Skip to main content

Trace Event Dispatch in Game Event Monitor

TinyGiants
TinyGiants
Unity Games & Tools Developer

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.

Find event references before entering Play Mode​

Find OnKeyPickedUp in Game Event Editor, open its Event Finder, and scan the current scene.

The List view shows the objects, components, and fields that reference the event. Select the door or pickup component's result to locate its Inspector configuration.

Event Finder listing objects and components that reference the event

For scenes with several doors, switch to Grouped view to check references by component type and confirm that the instances use the same event asset.

Event Finder results grouped by component type

Trace the event in Game Event Monitor​

Open Tools > TinyGiants > GES > Game Event Monitor and reproduce the pickup in Play Mode. Dashboard summarizes recorded dispatches, listeners, and warnings.

Game Event Monitor Dashboard and recent activity

For a slowdown, sort Performance by Avg Time or Max Time to identify events that need further measurement.

Performance with execution timing by event

Confirm the raise in Recent​

Search for OnKeyPickedUp in Recent and select a record. Details shows its name, type, time, frame, arguments, and caller when available. It also shows the stack trace if the record includes one.

Recent event raises in timestamp order

When several pickups or publishers share an event, check the key identifier and Called By to identify the source. Selecting an event in Statistics shows its total count, frequency, average interval, and last raise.

Check Warnings and Listeners​

Check Warnings for issues recorded while reproducing the problem. Use the event name to find its dispatch and listener records.

Warnings recorded by Game Event Monitor

If the event fired, look for the door's current subscription in Listeners and check when the object was enabled and registered. If the subscription is present, inspect the target method, arguments, and Action Condition.

Current listener information grouped by event

Verify connections in Automation​

If the pickup uses a Trigger or Chain to raise a separate door event, find the source in Automation and expand its branches. Check the current connection and target, then use Recent to see whether the target event fired.

Automation branches showing Trigger and Chain connections

Verify the key and door flow​

  1. Load the save and pick up the key again. Check the OnKeyPickedUp arguments in Recent.
  2. Check the door subscription in Listeners. If it is missing, check whether the door acquired the event asset and registered after it was enabled during loading.
  3. If initialization order caused the missing subscription, correct it and reproduce with the same save. Confirm that the new door listens to the same event and opens.

Open the monitoring demo