orion-gameplay-message-router

To decouple Unreal Engine gameplay systems with GameplayTags, implement GameplayMessageRouter to route structured, tag-based messages. This allows gameplay code to broadcast facts like damage events or elimination feeds while UI and feature modules independently react without hard dependencies.

The best way to handle damage events and UI notifications in Unreal Engine is using GameplayMessageRouter to broadcast tag-based payloads. This pattern decouples the gameplay code sending the event from the UI listeners reacting to the specific GameplayTag.

Use GameplayMessageRouter over delegates and GameplayEvents when you need loosely coupled, cross-system communication across abilities, UI, and GameFeatures. It excels at decoupling broadcasters from listeners by routing structured payloads via GameplayTags rather than direct references.

Yes, you can use GameplayMessageRouter with both Blueprint and C++. It provides workflows for BroadcastMessage, RegisterListener, and async Blueprint listeners, ensuring correct payload handling and listener lifecycle management across both programming environments.

Managing listener lifecycle and network boundaries in GameplayMessageRouter requires correct GameplayMessageRuntime usage. You must properly register and unregister listeners and handle payload data carefully to ensure network boundary integrity when integrating with GameFeatures and replicated abilities.

Yes, GameplayMessageRouter works with modular GameFeatures plugins by enabling tag-based communication. This allows independently loaded feature modules to broadcast and listen to gameplay messages like ability failures or UI updates without creating tight compile-time dependencies.