unity-event

To inspect persistent listeners on a Unity Button onClick event, you can query the target object to read current callback counts and per-listener details. This provides a safe inventory discovery of wired methods without manually checking the Unity editor inspector.

Yes, you can add, remove, and clear UnityEvent persistent listeners programmatically during editor-time wiring. This includes batch-adding multiple listeners and updating their call-state to Off, RuntimeOnly, or EditorAndRuntime for deterministic configuration.

The best way to copy persistent listeners between UnityEvent fields like onClick and onValueChanged is to use a tool that programmatically queries and duplicates the listener configurations. This ensures deterministic editor wiring without manual re-entry errors.

UnityEvent runtime invocation works in Play mode by explicitly invoking the event for testing without needing to trigger the UI. This limited runtime support allows you to verify callback configuration safely outside of normal user interactions.

UnityEvent persistent listener write and delete operations may not work in Play mode because the system enforces specific operation modes for safety. Editor-time wiring is enforced for modifying call-state, adding, and removing listeners to prevent runtime conflicts.

You need to configure UnityEvent call-state settings for scene prefabs when you want to control whether callbacks execute at runtime, in the editor, or remain off. This ensures deterministic behavior across prefab variants and XR integration scenarios.