> ## Documentation Index
> Fetch the complete documentation index at: https://docs.summerengine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Add in-game text chat

> Add text chat to a Summer Engine multiplayer game: one chat per match or up to 64 channels per World. Summer filters messages and applies blocks and rate limits.

Give everyone in a match a shared text chat. Summer handles the hard parts:
it filters messages, hides messages from players someone has blocked, slows
down spammers and keeps messages for 24 hours. Your game only draws the chat
box. Chat never goes through your game's server, so you don't have to
moderate anything yourself.

## Games like this

> [card] League of Legends
>
> Chat with everyone in the match.

> [card] Among Us
>
> Everyone talks it over during a meeting.

> [card] Minecraft servers
>
> One chat for everyone on the server.

> [card] World of Warcraft
>
> Separate channels for general talk and trading.

## What your players get

![A player sends a message; Summer filters it and applies blocks, then everyone in the World sees it. The game's server is not involved.](https://mintcdn.com/summer-18f03259/_ENGS2HrEIacSS6a/images/guide-art/chat/flow-light.svg?fit=max\&auto=format\&n=_ENGS2HrEIacSS6a\&q=85\&s=4c7fd4560afeccdff61a8f1862d4073d)

* **One chat for the match:** everyone in the World sees each message with
  the author's name.
* **Recent messages when they open it:** players who open the chat see the
  latest messages, and can scroll back a little further.
* **A safe chat:** a message the filter stops is never shown to anyone, and
  the sender is told it wasn't sent. When a player blocks someone, that
  person's messages disappear for them.

## Pick your setup

### One chat for the whole match

Every player in the match opens the same channel and talks to everyone. Good
for most games: team shooters, party games, survival servers.

![A message that passes the filter appears for everyone; a message the filter stops is not shown, and only the sender sees that it wasn't sent.](https://mintcdn.com/summer-18f03259/_ENGS2HrEIacSS6a/images/guide-art/chat/filtered-light.svg?fit=max\&auto=format\&n=_ENGS2HrEIacSS6a\&q=85\&s=510943534cee906affdc5a538a3067bd)

**Add match chat.** A chat box everyone in the match shares, with names and a filter.

In my Summer project, add a text chat that everyone in the match shares. Use
the Summer `summer-world-chat` skill; if you don't have it installed, find it
in the Summer library.

* Show each message with the author's name, as plain text.
* Open chat once the player has joined the match.
* If a message isn't sent, tell the player why; if chat isn't available, hide
  the chat box and keep the game working.

Read my project first and fit the chat box into my existing HUD. Then test it
with Local Play and tell me what I can only check once the game is hosted.

### Several channels in one world

A world can have up to 64 channels, each with its own name, such as
`general` and `trade`. Every player in the world can open any of them, so
channels work like topics on a busy server, not private rooms.

**Add chat channels.** Topic channels such as general and trade in my world.

In my Summer project, give my world the chat channels \[CHANNELS, for example
"general and trade"]. Use the Summer `summer-world-chat` skill; if you don't
have it installed, find it in the Summer library.

* Players switch between channels with tabs.
* Show unread messages on the tabs.
* If chat isn't available, hide it and keep the game working.

Read my project first and fit this into my existing HUD. Then test it with
Local Play and tell me what I can only check once the game is hosted.

Messages between friends outside a match are
[direct messages](https://docs.summerengine.com/build/friends.md), and party chat lives in the Summer app.

## Not sure which fits?

**Plan chat for my game.** Your agent reads your project and proposes how chat should work. No code.

Read my Summer project and help me plan its text chat. Use the Summer
`summer-world-chat` and `summer-friends` skills; if you don't have them
installed, find them in the Summer library. Don't change any files yet.

Tell me:

1. which chats my game should have: one match chat, several channels, or
   direct messages between friends;
2. where the chat appears on screen during play, and when it's hidden;
3. anything my design needs that chat doesn't cover yet, and how we can build
   around it.

## Testing it on your machine

Under Local Play, chat reports that it isn't available, so build the "chat
hidden" version first and check your game keeps working without it. Real chat
works in a hosted game: test it with two accounts in the same match.

## Technical reference

Exact methods, inputs and signals: [`Summer.client.channels`](https://docs.summerengine.com/api-reference/gdscript/client/channels), [`Summer.client.messages`](https://docs.summerengine.com/api-reference/gdscript/client/messages) for direct messages.

***

Does this not help you? [Reach out on Discord!](https://discord.gg/summerengine)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.