The Chat System provides in-game text communication for multiplayer sessions. It supports global, team, party, private, and system messages, with server-side distribution and client-side UI features such as mute, player list, clear chat, and console-command auto-completion.

For shared setup guidance, see the Migration Guide and Integration Guide. Use the System Atlas to look up functions, variables, events, components, and ownership references. Use this page for Chat System-specific components, message routing, validation, and UI behavior.

Related Videos

Some videos may have been recorded before V4. The same principles still apply, but asset names, component names, and folder locations may differ. Treat the current written documentation and V4 names as the source of truth.

• Play

• Play

Core Concepts

Components

Message Categories

Team, party, and private messages require Console Command System integration in the current implementation.

Console Command Integration

The current implementation uses the Console Command System for team, party, and private messages. The chat input detects slash commands and routes them to the command system before the Chat Manager distributes the resulting message.

1. The player types a command, such as /team Hello team.
2. The Chat Communicator detects the / prefix.
3. The Console Command System processes the command.
4. The command system calls the Chat System with the correct category and content.
5. The Chat Manager sends the message to the correct recipients.

Supported command examples:

• /team : Send a message to all teammates.
• /party : Send a message to party members.
• /whisper : Send a private message to one player.

A chat-only implementation is also possible. In that setup, the UI would provide direct category selection, and category routing would be implemented directly in the Chat Communicator and Chat Manager instead of using slash commands.

Message Flow

1. Client sender: The player submits text through the chat UI.
2. Chat Communicator: Converts the input into a server RPC with message content, category, and target if applicable.
3. Server Chat Manager: Validates the message and determines recipients.
4. Server distribution: Sends the message to the correct recipients through client RPCs.
5. Client recipient: Receives the message, checks the local mute list, and displays the message if the sender is not muted.

Server Validation

AC_GS_Chat_Manager includes a configurable banned word list for content moderation.

• The banned word list is an array of strings on the Chat Manager.
• When a player sends a message, the server checks whether the message contains any banned words.
• If a banned word is detected, the message is blocked and the sender receives a notification.
• If no banned word is detected, recipient filtering and distribution continue.

Additional validation can be added before distribution:

• Advanced profanity filtering: Pattern matching or third-party moderation.
• Rate limiting: Reject messages when a player sends too many in a time window.
• Permission checks: Prevent server-muted players from sending messages.
• Content length limits: Reject messages over the configured character count.

UI Features

Auto-Completion Flow

1. The player types a partial command such as /te.
2. The Console Command System checks available commands that start with the partial input.
3. The UI displays a suggestion such as /team.
4. The player presses Tab or selects the suggestion.
5. The input box completes the command.

Setup

1. Add AC_GS_Chat_Manager to the GameState.
2. Add AC_PlayerController_Chat_Communicator to the PlayerController.
3. Ensure the Console Command System is present if you need team, party, private messaging, or auto-completion.
4. Create or configure the chat UI widget.
5. Bind the message input box to the Chat Communicator’s send message function.
6. Add a player-list toggle button.
7. Add a Clear Chat button.
8. Optionally add custom server validation to the Chat Manager’s message receive function.

Testing

1. Start a multiplayer session with multiple players.
2. Send a global message and verify all players receive it.
3. Send /team Hello team and verify only teammates receive it.
4. Send /whisper PlayerName Hi and verify only the target player receives it.
5. Mute a player and verify their messages no longer appear locally.
6. Toggle the player list on and off.
7. Type a partial command such as /te and press Tab to test auto-completion.

Example Use Cases

• Team coordination: A player sends /team Let’s attack point B; the Chat Manager sends it only to teammates.
• Private messaging: A player selects another player from the player list, which pre-fills /whisper PlayerB, then sends a private message.
• Mute toxic player: A player mutes another player locally; future messages from that sender are filtered only for the muting player.
• System announcement: Server or game mode logic sends a broadcast message such as Match starts in 30 seconds.
• Auto-complete command: A player types /te, selects /team, then completes the message.

See Also

• Console Command System: Handles slash commands and auto-completion.
• Team Manager: Provides team affiliation data for team-chat recipient filtering.
• Player Manager: Provides player list and player state data.
• HUD: Can integrate the chat UI widget for display.