MGP Console Bot
What the bot does:
Live console: every console line of your Gameserver appears in its Discord channel, a few seconds after it happens.
Console commands: operators type a command into the channel, for example
say Hello, and the bot sends it to the Gameserver.Start, stop, restart, kill: with buttons on a pinned control message or with slash commands.
Per-channel access: you decide which roles may control which Gameserver. Who may see a console is set with normal Discord channel permissions.
Before you start
- A Gameserver on mygameplatform
The bot reads the console through the User API, so it only works with Gameservers in your own mygameplatform account.
- A Discord server where you have the Manage Server permission
Only members with Manage Server (or Administrator) can link Gameservers and change the bot's settings.
- An API token
You create it in your mygameplatform account, see Step 3. The bot asks for it in a private popup — it never appears in the chat.
Step 1 — Invite the bot
Click the link below and select the Discord server where you want to use the bot:
The link already asks for the permissions the bot needs. After the bot has joined, type /mgp help to see the setup guide inside Discord.
Step 2 — Prepare a console channel
Create one text channel per Gameserver, for example #console-survival.
In that channel, the bot needs these permissions:
Permission | Why |
|---|---|
View Channel | To read the channel |
Send Messages | To post the console |
Embed Links | For the control message |
Read Message History | To react to your commands |
Add Reactions | To confirm commands with ✅ or ❌ |
Pin Messages | To pin the control message |
Who can see the console is up to you: set it with the normal channel permissions in .
Step 3 — Create an API token
The bot uses a personal API token to talk to mygameplatform. How to create one is described on the User API page. Choose these scopes:
Scope | Needed for |
|---|---|
| Required — list your Gameservers and read their status |
| Required — read the console |
| Required — check the token and its expiry date |
| Optional — start, stop, restart and kill |
| Optional — send console commands |
Without the optional scopes the bot still shows the console; the buttons or the console commands are switched off.
Step 4 — Link the channel to your Gameserver
Link a channel
Type the following command — in the console channel itself, or anywhere with the
channeloption:/mgp connect channel:#console-survivalA popup opens. Paste your API token (it starts with
mgp_pat_) and confirm.The bot checks the token and shows a list of your Gameservers, visible only to you. Pick the Gameserver for this channel.
The bot posts a control message with the status and the buttons Start, Stop, Restart and Kill and pins it. The live console starts.
Each channel shows exactly one Gameserver. To link more Gameservers, repeat the steps with another channel.
Step 5 — Choose who may control the Gameserver
Members with the Manage Server permission can always control every Gameserver. Everybody else needs an operator role:
Add an operator role
For one Gameserver only:
/mgp operator add role:@Survival-Team channel:#console-survivalFor all console channels of your Discord server, leave out the channel:
/mgp operator add role:@TeamCheck the result with
/mgp operator list. Remove a role with/mgp operator remove.
- See a console
Discord channel permissions. The bot does not change them.
- Control a Gameserver (operators and admins)
Buttons,
/mgp start,/mgp stop,/mgp restart,/mgp kill,/mgp paneland typing console commands into the channel.- Manage the bot (admins only)
/mgp connect,/mgp disconnect,/mgp key,/mgp status,/mgp operatorand/mgp logchannel. These handle API tokens, so they are limited to members with Manage Server.
Step 6 — Set a log channel (optional)
Every action — links, starts, stops, console commands — is then also posted there, together with warnings such as an expiring token. /mgp logchannel clear removes it again.
Using the console
Live console
Console lines are collected for about two seconds and posted as a code block.
Status changes such as Server running or Server stopped appear as a short notice and update the control message.
If the Gameserver prints more than Discord can show, the oldest lines are left out and the bot posts
… X lines skipped. The complete output stays in the log files of your Gameserver.If the connection drops, the bot reconnects on its own. While the Gameserver is stopped, it checks regularly and continues as soon as it runs again.
Tokens, keys and passwords that appear in the console in the form
NAME=valueare replaced by<hidden>before they are posted.
Sending console commands
Type the command into the console channel, exactly as you would in the console of the game panel, for example:
Each line of a message is one command — at most 10 lines per message and 1000 characters per line.
Commands are sent right away, without confirmation.
✅ under your message means the Gameserver received the command. Its answer shows up in the live console.
❌ without a reply: you are not an operator for this Gameserver. ❌ with a reply: the reason is in the reply, for example The server is not running.
At most 20 console commands per minute per Discord server, to protect your API token's request limit.
Start, stop, restart and kill
Use the buttons on the pinned control message, or the slash commands in the console channel:
Command | What it does |
|---|---|
| Starts the Gameserver |
| Stops the Gameserver |
| Restarts the Gameserver |
| Stops the Gameserver immediately, without saving. Asks for confirmation first. |
| Shows the status and the buttons at the bottom of the chat, only for you — no scrolling up to the pinned message |
Every action is announced in the console, for example 🔄 Restart sent by @Name.
Replace or remove a token
Expiry warning: 7 days before a token expires, the bot posts a warning in the console channel and the log channel.
Broken link: if a token stops working — expired, revoked or paused — the bot marks the link as broken and posts a notice. The bot checks every token regularly, so a revoked token is noticed within minutes.
New token: create a new token and enter it with
/mgp key channel:#console-survival. The link works again right away.Disconnect:
/mgp disconnect channel:#console-survivalremoves the link and deletes the stored token.
/mgp status shows all linked channels with their token (last 4 characters), expiry date and operators.
What the bot stores
Your API token, encrypted. Only its last 4 characters are stored readable, so you can recognise it.
Settings: linked channels and Gameservers, operator roles and the log channel.
Action log: who did what and when, including console commands, kept for 90 days. Arguments of common login and password commands (such as
registerorchangepassword) are not written to the log.If you remove the bot from your Discord server, all settings and tokens of that server are deleted. Deleting a console channel removes its link.
Commands
Command | Who | What it does |
|---|---|---|
| Everyone | Short help; admins get the setup guide. Admins can post it in a channel with |
| Admins | Link a channel to a Gameserver |
| Admins | Remove a link and delete its token |
| Admins | Replace the token of a link |
| Admins | Overview of all links, tokens and operators |
| Admins | Allow or remove an operator role |
| Admins | Show who may control which Gameserver |
| Admins | Set or remove the log channel |
| Operators | Control the Gameserver of the current channel |
| Operators | Status and buttons, only for you |
Admins are members with the Manage Server permission.
Troubleshooting
The /mgp commands do not show up
New commands can take up to an hour to appear. Reload Discord with Ctrl+R and check that the bot is online.
"You're not an operator for this server"
You have neither the Manage Server permission nor an operator role for this channel.
Fix: An admin adds one of your roles with /mgp operator add (see Step 5).
"The bot is missing these permissions"
The bot cannot work in this channel.
Fix: Give the bot the permissions listed in Step 2 in the channel settings.
"Couldn't pin the control message"
Pinning needs its own Discord permission, Pin Messages. Manage Messages is not enough.
Fix: Give the bot Pin Messages in the channel, or pin the control message yourself.
"The link to … has stopped working"
The API token expired, was revoked or is paused.
Fix: Resume a paused token in the API Tokens tab of your account. Otherwise create a new token and enter it with /mgp key (see Replace or remove a token).
"The server is not running"
Console commands only work while the Gameserver is running.
Fix: Start it with /mgp start or the Start button.
"Limit reached"
More than 20 console commands were sent within a minute in your Discord server.
Fix: Wait the number of seconds named in the reply.
Buttons are greyed out
The token has no servers:control scope, or the link is broken.
Fix: Create a token with servers:control and enter it with /mgp key.