Understanding the Decoupled Flow

Separating backend routing from frontend presentation

The MP_ChatSystem is built on a strictly decoupled architecture. The C++ backend handles data routing, security, and memory management, but it does not dictate how your game looks.

Separation of Concerns

  1. 1
    The UI does not send messages directly: It calls SendMessage on the MP_ChatClient component.
  2. 2
    The UI does not store chat history: The server holds the official FastArray. Your UI merely displays what the server pushes.
  3. 3
    The UI is event-driven: You do not need to use EventTick. The component fires an Event Dispatcher the millisecond a message arrives.

Performance Tip

By keeping the UI lightweight, you guarantee that high-volume chat traffic will never bottleneck your game's framerate.

← Auto-routingOverviewEvent Binding →