Discord Bot Commands Reference

How to read this reference

The bot has 46 top-level commands. Several have subcommands, so there are 96 things you can actually type. All 96 are listed below.

Each table has four columns that matter:

• Level - the access level a member needs, granted with /config role. See Discord Bot Permissions & Security.
• Scope - the API scope the linked key must carry. Missing scope means the command fails no matter what Discord level you hold.
• Reply - Public means the whole channel sees the answer. Private means only you do.
• Options - [optional], <required>.

Every command except /chat-unlink accepts an optional server-id. Leave it out and the bot uses the server bound to the channel, then the Discord server default. If neither is set it says so.

Two limits apply to everyone: 5 seconds between uses of the same command by the same person, and 5 commands running at once per Discord server. /help is exempt from both.

Servers and status

/servers is where everyone starts - it lists your servers with their ids, and every other command needs one of those ids or a channel binding.

/players calls two endpoints and needs both players:read and servers:read. If the key holds only one of them the command still answers, but reports "contents not reported" instead of the list.

Lifecycle

/auto-restart behaves as two commands. With no hours, it shows the current schedule and needs only Read Only and servers:read. With hours (6, 12 or 24), it sets the schedule and needs Full Access and servers:write.

Lifecycle replies are public on purpose - the channel should be able to see who restarted the server.

Console

lines accepts 1 to 50 and defaults to a recent window.

Both are private, and both need Console Access rather than Read Only. Console output can contain RCON and admin passwords, and a command like a 7 Days to Die getgameprefs or a Valheim bridge dump prints configuration wholesale. Credentials and IP addresses are redacted before anything is posted, but the reply is still kept private to the person who ran it.

/config command-channel can restrict /command to a single channel. It does not restrict /console.

Backups

Four separate scopes, and none implies another. A key with backups:read alone can list but not create; one with backups:write can delete but not restore. Grant only what you want the bot able to do - leaving backups:restore off is a reasonable way to make sure nobody overwrites live data from Discord.

/backups create waits for the backup to finish, which on a large world can take a couple of minutes.

Settings

/settings set needs both scopes: it reads the schema to validate your value before writing it.

When a setting needs a restart to take effect, the reply carries a Restart Now button. Pressing it re-checks that you still hold Full Access, and needs servers:lifecycle on the key.

Mods

provider is one of nexusmods, curseforge or steamworkshop. Which are available depends on the game - /mods search without a provider tells you which ones your server supports.

Windrose Plus

windrose:admin also permits reading the RCON password in clear text over the API. Treat any key holding it as a credential in its own right.

`/windrose` is a Windrose Plus admin command and stays one. The economy on Windrose runs on the same shared /balance, /shop, /buy, /link and admin commands every other game uses — there are no /windrose economy verbs and none are planned. Enabling Windrose Plus is, however, what makes the economy available on a Windrose server, so /windrose enable is the first step to having one. See Windrose Economy and Shop.

Live map

Every reply is private except one, and both halves of that are deliberate. /map players says where each player is standing. In a public channel that is a map of everybody's base handed to whoever is in the room, including the person who built the raid party. /map leaderboard is the exception: it carries no positions and no platform identifiers, it is about a finished wipe rather than a live world, and posting it into a community's own channel is the point of having it.

`/map share` never prints the link. It says whether a public map link is active and roughly when it expires, and nothing else — the URL is a credential for an unauthenticated view of your world, and a chat message is not a place to keep one. Creating and revoking a link are owner actions in the panel, on the page where the revoke button sits next to it.

`/map` is read-only and stays that way. The panel's map can teleport a player, spawn an entity, call a horde and reset a region. None of those is a chat command. Teleport and spawn move or surprise people who are playing right now, and an admin doing that from a panel is looking at the consequence while one typing into Discord is not. Resetting a region destroys everything built in a 512 x 512 block area — it is gated on a backup that has to finish first and on an owner-only permission, and a Discord role is not a GameGrid permission, so the bot cannot check the gate that action depends on.

/map region is 7 Days to Die only. Other games answer with what their map does have — read /map status first.

Account, billing and support - Owner only

These four look like reads and are gated at Owner, the highest level, because they expose account and billing information. Full Access is not enough. billing:read is also missing from the "Discord Bot" scope preset, so /billing is the command most likely to fail on a freshly made key.

Economy - player commands

These are Read Only on purpose. They are player actions on the player's own wallet, so ordinary members can use them without being given any control over your servers. /help-economy needs no level and works before /setup has been run.

/shop and /buy suggest your own shop's categories and items as you type. quantity on /buy accepts 1 to 100.

`character` on `/link` is optional on most games and required on Windrose. Windrose has no in-game chat the platform can read, so instead of typing !link CODE in game the player names their character and joins the server — the link completes when that character is seen online. On every other game the option is ignored; the name is read from the !link message itself. If a game needs it and it is missing, the bot says so and no code is sent.

Economy - admin commands

`/economy-setup` and `/economy-config` are not level-gated. Like the /config subcommands, they are limited to the person who ran /setup and the Discord server owner. A Full Access holder is refused.

/shop-admin takes add, remove, list or edit as its action. /economy-earn takes enabled, playtime, kill, death, level, event or max.

`/award` only adds currency. The amount option has a minimum of 1, so Discord refuses a negative number before the command is even submitted. To take currency away, use the panel.

Chat bridge

/chat-link accepts a normal text channel only. /chat-unlink deliberately takes no options - it unlinks whatever this Discord server has bridged.

Setting up the bridge needs economy:read, but running it needs economy:write as well. A key with only economy:read links successfully, then carries game chat into Discord while messages typed in Discord silently never arrive. If that is what you are seeing, check the scope before anything else.

See Discord Chat Bridge for how the bridge behaves once it is running.

Config presets and scheduled events

Presets are saved sets of settings; events apply a preset for a window of time and revert it afterwards - a 2x XP weekend, say.

/preset create link returns the panel URL for building a preset - presets are created in the panel, not in Discord. It needs no access level.

/preset apply is the one command needing two scopes: it creates an event and starts it immediately, and rolls the event back if the start fails.

Every /preset and /event reply is public, including refusals. A member without the required level sees "you need at least Read Only permission" posted in the channel rather than privately.

/preset view hides values that look like credentials. It deliberately does not hide things that look like IP addresses, because a game version such as 1.20.4.1 has the same shape.

Command Schedule (/command-schedule)

Manage scheduled recurring console commands from Discord. These commands let you create, list, edit, delete, toggle, run, and view the history of command schedules without opening the panel.

The command option takes a command ID from the catalog (e.g. saveworld, say, shutdown). Use /command-schedule catalog to see the available commands for your game.

The cron option takes a 5-field cron expression in UTC (e.g. 0 4 * * * for daily at 4 AM UTC, 0 * * * * for hourly, 0 0 * * 0 for weekly on Sunday). The minimum interval is 5 minutes.

The params option takes a JSON string (e.g. {"message":"Hello world"}). Use /command-schedule catalog to see which commands take parameters and what they are.

The timezone option takes an IANA timezone name (e.g. America/New_York). Defaults to UTC if omitted.

Examples:

• /command-schedule create name:"Daily Save" command:saveworld cron:"0 4 * * *" timezone:"America/New_York" — Save the world daily at 4 AM EST.
• /command-schedule create name:"Hourly Announcement" command:say cron:"0 * * * *" params:"{\"message\":\"Server restarting soon\"}" — Broadcast a message every hour.
• /command-schedule run schedule-id:"abc12345" — Run a schedule immediately.
• /command-schedule history schedule-id:"abc12345" — View the last 10 executions.

Setup and configuration

These are not gated by access level at all. /setup needs Discord's Manage Server permission the first time; every /config subcommand is limited to the person who ran `/setup` and the Discord server owner. All reply privately.

A successful `/setup` re-link clears every role grant, channel binding and live mirror. Run /config view and /config live-list first so you can put them back. Your log, alert and command channels and default server survive.

Help

/help shows the caller their own access level and the commands it allows, which makes it the quickest way to answer "why can't I do this". It is exempt from the cooldown and the concurrency limit, so it always answers.

When a command is refused

Two different systems can refuse a command, and the message tells you which.

The two gates are independent. Full Access with a key missing the scope fails, and a key with every scope grants nothing to a member the Discord gate refuses. See Discord Bot Permissions & Security.