Messenger – Type-Safe Event System for Unity

Publisher

Invariant

Please Note

This entry is from Wednesday May 6, 2026. The price of the asset may have changed since then.
Please visit our homepage for recent offers and sales. Official and private Unity Asset Store™ sales usually last about 14 days.

Overview

Stop wiring unrelated systems together with direct references, static globals, or fragile string events!

Messenger is a code-first, type-safe event system for Unity that helps you decouple gameplay, UI, audio, analytics, meta, and service systems without string keys, enum registries, or hard references.

Use Messenger as a local event system in pure C#, inject it through your composition root, or share ScriptableObject Channel assets across prefabs and scenes when you want Inspector-friendly communication without singletons.

Why choose Messenger:

• Strongly typed messages for safer refactoring and cleaner APIs
• Explicit Send(in T) and Signal<T>() flows for payload messages and no-data signals
• High-performance, low-allocation dispatch with cached signals and benchmarked runtime behavior
• Fluent subscriptions with a single IDisposable for lifecycle cleanup
• ScriptableObject Channels for cross-scene and cross-prefab messaging
• Optional logging, exception handling, thread safety, capacity tuning, and custom cache support
• DI-friendly IMessenger interface with examples for Zenject, VContainer, Reflex, and pure DI
• Re-entrancy-safe dispatch with deferred subscribe/unsubscribe during message processing
• Extensive documentation, 4 sample scenes, 469 tests, benchmarks, and zero external dependencies

Messenger is built for teams that want scalable architecture without heavyweight frameworks: from small projects that need cleaner communication to larger codebases that need predictable behavior, low overhead, and easier testing.