Home

---

title: Home description: Decoupled, simple systems for Unity template: home.html hide:

• navigation
• toc

---

AI Assistance Disclosure

DxMessaging began as an original project around 2014 and remains actively developed and used today. Over the past two years, I (wallstop) have been using LLMs to help improve the library's quality and performance, expand its tests, and create user-facing documentation. There is always a human in the loop: I actively review all changes and read through all user-facing copy. I share this so you can make an informed decision about using the project.

DxMessaging is free and will remain free forever. No paid editions, paid upgrades, or feature charges.

Start Here

• Getting-Started-Quick-Start - Define, register, and emit your first message.
• Concepts-Mental-Model - Choose between untargeted, targeted, and broadcast messages.
• Guides-Diagnostics#message-monitor - Inspect emissions, filters, contexts, and captured call sites.
• Guides-Diagnostics#flow-graph - Inspect loaded-scene MessagingComponent routes and delivery evidence.
• Guides-Inspector-Overlay - Catch base-call mistakes and inspect component-local diagnostics.
• Architecture-Performance - Read the current published benchmark tables.

Install

OpenUPM

openupm add com.wallstop-studios.dxmessaging

Git URL

https://github.com/Ambiguous-Interactive/DxMessaging.git

See the Getting-Started-Install for scoped registry, Git URL, and local tarball options.

Why Teams Use It

Simple primitives

Three message shapes - untargeted, targeted, broadcast - and nothing else to learn. Each contract is an explicit typed struct, and no system holds a reference to any other.

Easy to use

Define a struct, register a handler, emit. Registration tokens follow their owner's lifecycle, so handlers remove themselves - no manual unsubscribe, no leaked listeners.

Small edits, big impact

The same simple primitives decouple entire systems. Wiring a feature in is one registration; removing it is deleting that line. Interceptors, handler priorities, and global observers layer on without touching existing code.

High performance

Struct messages and readonly by-reference handlers keep steady-state dispatch at zero allocation. Type-indexed routing stays O(1); see the current CI table for measured scenario costs.

Next

• New to the package: Getting-Started
• Choosing message types: Concepts-Message-Types
• Unity integration patterns: Guides-Unity-Integration
• Debugging message flow: Guides-Diagnostics
• API details: Reference-Reference