Skip to content

Live Event Debugging

Available from

InspectMe Pro introduces Live Event Debugging, a powerful feature that allows you to trigger and inspect any event in real time, directly from the Unity Editor. This includes standard delegates like Action, Func<T>, custom-defined delegates, and Unity’s UnityEvent system.

This feature is especially useful for debugging signal flows, testing event-driven behavior, and verifying runtime event bindings — all without writing temporary code or rerunning play mode.

Feature Summary

  • Trigger any supported event signature directly from the inspector.
  • Input parameters dynamically before invocation.
  • View and inspect return values after event execution.
  • Track attached listeners and method targets.
  • Monitor listener count using Watchers for runtime debugging.

Supported Signatures

Live Event Debugging supports a broad range of delegate types and UnityEvents. This includes both parameterless and parameterized forms of:

  • Action
  • Func<T>
  • Func<T1, T2, TResult>
  • UnityEvent and UnityEvent<T>
  • Custom delegate types (e.g. Predicate<T>, Comparison<T>)

Full compatibility and use cases are covered in the Supported Event Types reference.

Return Values

When invoking a delegate or event that returns a value (such as a Func<T>), InspectMe will display the result under the invocation section.

If the delegate has multiple listeners, only the return value from the last listener is returned. This is not a limitation of InspectMe—it is the standard behavior of .NET delegates. For an in-depth explanation with code examples, see Return Value Behavior.

Integration with Watchers

InspectMe allows you to attach Watchers to Event nodes to monitor changes in their listener count. This works similarly to Watchers for collections, triggering whenever a listener is added or removed. To learn how this integrates into the debugging workflow, see Watcher Integration.


For any queries or support regarding Live Event Debugging feature, please refer to our Support section or visit our FAQ page.