How emre-emiroglu/hmsignalbus works
Project type and purpose
• This is a Unity runtime package (installed via UPM) that implements an in-engine, event-driven “signal bus” following the publish-subscribe pattern. Its sole purpose is to provide loose-coupled messaging between components in a Unity project.
File structure
• Top-level files: LICENSE.md, README.md, package.json ⇒ metadata for a Unity Package
• Runtime/… : contains three C# scripts and their Unity asmdef ⇒ core implementation that ships in the package
• SignalBus.cs: the core bus managing declarations, subscriptions, and firing
• SignalBinding.cs: per-signal registry handling subscriber lists, priority ordering, and invocation
• SignalBusUtilities.cs: static façade & bootstrapper (uses Unity’s RuntimeInitializeOnLoad to create the singleton bus before any scene loads)
README for insights
• Confirms pub-sub features: Declare, Subscribe (with priority), Unsubscribe, Fire
• Explains exceptions and warnings for misuse
• Highlights the use of Unity attributes to guarantee bus initialization
Main components and their interactions
a. Unity Runtime Initialization
• Unity’s engine loads code marked with [RuntimeInitializeOnLoadMethod] in SignalBusUtilities ⇒ creates a singleton SignalBus instance before scene load
b. SignalBusUtilities (static façade)
• Exposes Declare<T>, Subscribe<T>, Unsubscribe<T>, Fire<T> methods
• Delegates all calls to the underlying SignalBus instance
c. SignalBus
• Manages a dictionary of SignalBinding<T> by signal type T
• On Declare<T>: creates a new SignalBinding<T> entry (or throws if already declared)
• On Subscribe/Unsubscribe/Fire<T>: finds the SignalBinding<T> and calls its Add/Remove/Invoke
d. SignalBinding<T>
• Holds an ordered list of subscriber callbacks plus priority
• Implements Add (with priority), Remove, Invoke (in priority order), HasReceivers
e. Client Components (any MonoBehaviour / C# class in the user’s game code)
• Call SignalBusUtilities.Declare<MySignal>() at startup
• Subscribe/unsubscribe methods using SignalBusUtilities
• Fire new signal instances via SignalBusUtilities.Fire(new MySignal())
Architectural patterns & principles
• Pub-sub / observer pattern for loose coupling
• Singleton service (SignalBus) managed by a static façade (SignalBusUtilities)
• Generic registry per signal type for type safety and zero-reflection at runtime
• Early initialization via Unity lifecycle hooks to avoid manual bootstrap
Final checklist
• Clear component labels: class names and roles
• Optional inset showing the Tests folder’s EditMode and PlayMode tests invoking the public API for validation