Help In Discord

Slash commands

Eight commands for things you do from inside Discord, how to let people run Minecraft commands, and your own console on the dashboard.

The /relay commands

Everything that configures BedrockRelay is on the dashboard. These commands are for things you do in Discord, in a channel connected to a Minecraft world. Plugins add more.

CommandWhoWhat it does
/relay onlineAnyoneShows who's playing in this channel's Minecraft worlds.
/relay runAllowed rolesRuns a Minecraft command, if it's been allowed. See below.
/relay modChosen rolesWarns, kicks, mutes or bans a player, or lifts a mute or ban. See Moderating from Discord.
/relay farmbotChosen rolesMoves the world's FarmBot to where a player is standing, to keep a farm running, or sends it back. See FarmBot.
/relay linkAnyoneLinks your Discord account to your Xbox account by signing in with Microsoft, or shows and undoes your link. See Linking accounts.
/relay accountsAnyoneA private list of all your links: your dashboard and each world you own, with its map and mcBedrock page, the worlds you play on, your BedrockMap account and your mcBedrock profile. Works in any channel. See Your links.
/relay dashboardManage ServerA private link to this Discord server's dashboard page, and a list of what's connected here.
/relay disconnectManage ServerDisconnects this channel from its Minecraft worlds straight away, whoever owns them. Your emergency brake.

Command descriptions appear in each member's own Discord language.

While a world's owner has switched relaying off, commands that reach the game answer that relaying is off instead.

Who can use what

Each Minecraft world's Permissions tab is where its owner chooses who can use which commands in Discord:

  • Moderation: for each thing /relay mod can do (warn, kick, mute and ban), the roles allowed to do it. Unmuting goes with muting, and unbanning with banning. See Moderating from Discord.
  • FarmBot: the roles that can move the world's FarmBot with /relay farmbot. See FarmBot.
  • Plugin commands: for each installed plugin that has commands, the roles that can use them. Discord administrators always can. See Plugins.
  • Minecraft commands: which commands /relay run may run, and for whom. See below.
The Moderation card on a world's Permissions tab: Warn, Kick, Mute and Ban, each with the roles allowed to do it and a list to add another
Add the roles allowed to do each. The owner can always do everything.

The roles come from every Discord server the world is connected to. On a Discord server's own page, the Permissions tab shows who can do what there, for each world connected to it. Only each world's owner can change it.

Running Minecraft commands from Discord

/relay run refuses everything until you allow specific commands. Open the Minecraft world's page in the dashboard, go to the Permissions tab, and under Minecraft commands add a rule for each command, such as weather, time or say.

The Minecraft commands card on the Permissions tab, listing allowed commands and who can run each, with the form for adding a rule
Each rule allows one command, for administrators or a role you choose.
  • Administrators only lets anyone with Discord's Administrator permission run it.
  • Choosing a role also lets that role's members run it. Roles come from the Discord servers the world is connected to.
  • * allows every command, including op, deop and stop. Only pair it with a role you trust completely.

Type the command without its slash: /relay run command: weather clear. The answer shows what Minecraft replied. If the channel relays more than one Minecraft world, choose which with the world option.

Only the world's owner can change these rules.

Other addons' commands

Commands from your other addons work too, such as aw:option: allow them by name like any other. They run without a player behind them, so a command that changes a player's own settings needs to be told who: execute as Steve run aw:option 12. That needs both execute and aw:option allowed. Allowing execute only lets it run commands you've allowed too.

Commands an addon keeps for admins can't be run from Discord. Discord only says whether a command worked, not what the addon replied, so check in the game.

The console on the dashboard

As a world's owner, you can run any Minecraft command from the dashboard, with no rules to set up first. Open the world's page, go to the Permissions tab, type the command into Console and press Enter. The slash is optional. Up and Down bring back what you ran this visit.

The Console card on the Permissions tab: the notice about its limits, the command box, and three commands run this visit, two done and one failed with its syntax error
Each command shows whether it worked. A mistyped one shows Minecraft's error.

It works on servers and Realms, and on a Realm it works with cheats off. It isn't quite the server's own console:

  • You see whether it worked, not what it printed. Minecraft doesn't give a script a command's output, so check in the game for the result. Ran, changed nothing means it was valid but affected nothing, like kill @e[type=cow] with no cows loaded.
  • It runs as the world, not as a player. @s matches nobody and ~ ~ ~ is 0, 0, 0 in the Overworld, so name players and give coordinates.
  • Some commands only the server's own console accepts, such as stop, allowlist and permission. They can't be run from here.
  • No answer means the world didn't reply in time, so the command may or may not have run.

The console waits, with a line saying why, while the world can't be reached: a server that isn't connected, or a Realm our bot isn't in (it's joining, it left because nobody's playing, or relaying is switched off).

Only the owner sees the console, and every command run from it is recorded. Discord administrators don't get it; they use /relay run.

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

Open the dashboard