Help In Discord

Channels and events

Each connected channel chooses which way messages go and what it hears.

Connecting channels

You choose your first channel at the end of setup. To add more, open the Discord server in the dashboard's sidebar, go to its Channel routes tab and use Add a channel route. Manage channels on a Minecraft world's page takes you there too. Each channel's settings save as you change them.

A connected channel on the Discord server page, showing its direction, its event checkboxes and the Shared chat switch
Each channel has its own direction (1), events (2) and shared chat (3).

A common setup is #minecraft-chat with Chat both ways, plus a #server-log that's Minecraft → Discord only, with Join, Leave, Death and Connection notices.

Direction

SettingWhat it does
Both waysMinecraft messages appear in the channel, and the channel's messages appear in Minecraft.
Minecraft → DiscordA read-only feed, useful for logs.
Discord → MinecraftThe channel talks into the game without showing its chat.

Events

EventWhat the channel receives
ChatPlayer chat, posted as the player with their head as the picture. Also decides whether the channel's own messages go into Minecraft.
Join / LeaveA notice when a player joins or leaves.
DeathA notice when a player dies, and how.
Connection noticesA notice when the world connects, one if it goes offline (three minutes without a check-in), and one when it's back. Nothing in between.
Other addonsMessages that other addons in your world send to Discord. See the developer guide.
Holobuild buildsWorlds with Bedrock Holobuild: a card for each build, with a picture of the blueprint, kept up to date as it goes up, and a card for each new blueprint.
ModerationWho was warned, kicked, muted, banned or removed, by whom and why; bans and mutes lifted or running out; and banned players trying to join (at most once an hour each). See Moderating a player. Tick it only on a staff channel: it isn't included when a channel gets every event.
Realm StoriesRealms only. What the Realm's Stories feed shows, as it happens: the game's own events, like a player first reaching the End or someone new joining the Realm, and what members post there, screenshots included, as the player who posted it. Like Moderation, it isn't included when a channel gets every event: tick it by name.

Joins, leaves, deaths and notices are posted under the world's name with the BedrockRelay logo as the picture. To use your own, such as your world's logo, open the world's Settings tab and choose a picture under Picture in Discord. It's cropped to a square, and new posts use it straight away.

You can also connect a channel with no events ticked. It then gets only the plugin posts you send to it, which suits a staff channel for alerts.

Shared chat

When a Minecraft world is connected to more than one channel (in two Discord servers, say), Shared chat also copies people's Discord messages between those channels, so everyone can talk to each other as well as to Minecraft. Every channel involved has to turn it on; it's off by default. Edits and deletions aren't copied.

It works the other way round too: several Minecraft worlds can share one channel. Slash commands in that channel then ask which world you mean.

Messages from bots and webhooks

Only messages that people type reach Minecraft. Messages from other bots, webhooks and followed announcement channels are left out, so two relays can't echo each other forever.

To let one in, open Messages from bots and webhooks on the channel's route and choose it from the list. It then shows ticked above the list; untick it to keep it out again. This suits things like a weather service, a GitHub feed or announcements followed from another Discord server. The list shows the channel's webhooks, with who made them, and any bot that has posted there since BedrockRelay joined. A bot that hasn't posted yet appears after its first message. Each route has its own list, so in a channel shared by several worlds you choose which ones hear it.

  • Only let in ones you trust. Anyone who has a webhook's address can post through it, under any name.
  • Never let in another bridge that posts Minecraft chat, or messages will go round in circles.
  • BedrockRelay's own messages and webhooks never go back into the game, and never appear in the list.

How it looks in Minecraft

  • Discord messages appear as [Discord] Name: message, with the name in the colour of the person's highest Discord role.
  • Discord bold, italic, underline, strikethrough and code are shown with Minecraft's own formatting.
  • Chat that starts with ! stays in Minecraft and isn't sent to Discord, which suits other addons' chat commands. You can change this on the world's Settings tab, under Chat from Minecraft.
  • From Minecraft, @everyone, @here and role mentions are defused, so nobody can ping a whole Discord server from the game.
  • Messages from other bots and webhooks are left out unless you let them in.

When BedrockRelay can't use a channel

When you add BedrockRelay, Discord gives it a role called BedrockRelay with the permissions it asked for. That role applies across the whole Discord server, but each channel can override it. Private channels, and channels that take permissions away from @everyone or certain roles, can take them away from BedrockRelay too.

If that role is missing any of them, for example because BedrockRelay was added before it asked for a newer one, your Discord server's page says so, and Update permissions on its Settings tab takes you to Discord to approve them again.

In every channel it relays, BedrockRelay needs:

  • View Channel, to see the channel and read what people say for Minecraft.
  • Manage Webhooks, to post each message under the player's name and head.

The dashboard checks this for you. Channels BedrockRelay can't use are greyed out when you choose one, and a connected channel that later loses a permission shows a warning on its route.

To fix a channel:

  1. In Discord, open the channel's settings (the cog next to its name) and choose Permissions.
  2. Add the BedrockRelay role to the list of roles and members.
  3. Set View Channel and Manage Webhooks to allowed (the green tick), and save.
  4. Back in the dashboard, choose Check again.

If the channel takes its permissions from its category, you can make the same change on the category instead.

Connecting another Discord server

Only the person who set up a Minecraft world can connect it to channels, in any Discord server. In the dashboard, choose Set up a new world, pick the other Discord server and add the bot, then choose the same world: a dedicated server by its address, or a Realm with Use this one. Setup skips installing the pack and goes straight to choosing a channel. Once it's there, add more on that Discord server's Channel routes tab.

Anyone with Manage Server in a Discord server can still disconnect it from their own Discord server, from the dashboard or with /relay disconnect.

As the world's owner, you can disconnect it from any Discord server yourself, even one you've left or can't manage: on the world's Overview tab, choose Disconnect beside that Discord server. Its channels there stop relaying, and its live boards and voice rooms there stop. Nothing else in that Discord server changes.

Ready to connect a world, or need to change something?

Open the dashboard