Message System

Message System

The Core message subsystem provides tag-addressed typed communication.

Responsibilities

• register and remove listeners;
• broadcast a payload on a Gameplay Tag channel;
• retain diagnostic history where configured;
• expose native and Blueprint-facing operations;
• carry bridge payloads between optional feature plugins.

Messages are appropriate when publishers and receivers should not share a feature-module dependency. Payload type and tag are part of the contract; avoid using an unstructured message as a substitute for a clear domain API.

Relationship to other mechanisms

• Delegates are useful inside an existing dependency boundary.
• Interfaces express capabilities on concrete objects.
• Registries discover tagged assets or implementations.
• Event handlers resolve a tag to behavior with an explicit lifecycle.

These mechanisms complement one another and should not be collapsed into a single global event bus.