A chat bridge puts your server's conversation in a Discord channel and Discord's back in game. It keeps a community alive between sessions — and configured carelessly, it turns both sides into a feed nobody reads.
What to do
- Create a bot and get its token
The same Developer Portal process as any Discord bot. The bridge plugin is the bot's code; you supply the identity.
- Put the token in the plugin's config, not in a public place
It is a bot token, with everything that implies. The security article on tokens applies here exactly.
- Invite the bot to your server and give it the channel
It needs to read and send messages in the one channel you are bridging, and nothing else.
- Decide what crosses in each direction
This is the setting that matters, and it is covered below.
What to bridge and what to leave
| Event | Recommendation |
|---|---|
| Player chat | Both directions. This is the point. |
| Joins and leaves | One direction, into Discord, and only if your server is small. |
| Deaths | Fun on a small server, noise on a busy one. |
| Advancements | Leave them in game. |
| Server start and stop | Into Discord. Genuinely useful. |
| Console output | Never into a public channel. It contains more than you think. |
A message arriving from Discord shows a name that nobody in game can verify. If your bridge lets Discord users run commands, or if staff act on instructions «from an admin» in chat, that is an impersonation route. Show a clear Discord tag on bridged messages, and never let the bridge execute commands.
A single busy channel that people actually read beats five quiet ones. Joins, deaths and chat spread across separate channels look organised and get muted individually within a fortnight.
A message typed in game appears in Discord with the player's name, and a Discord message appears in game clearly marked as coming from Discord.