Features
Console
Watch the server console live in the dashboard, send commands, and get warnings and errors in a Discord channel.
Every connected Minecraft server has a console in the dashboard. You see the server's output live, send commands and set up buttons and schedules there. The bot can also post warnings and errors from the console to a Discord channel.
Set up
Console in the dashboard
- Connect the server as described under Chat sync.
- In the dashboard, open "Servers" and then your server.
- Open the "Console" tab. The "Live console" starts on its own.
- Type a command without a slash into the field, for example
list, and click "Run".
Out of the box the server only accepts whitelist add, whitelist remove and whitelist list. How to allow more is described under Commands from Discord.
Warnings in a Discord channel
- In the dashboard, open "Notices & reports".
- Under "Channels", pick the channel for "Console", for example
#console. This applies to all servers. - For a single server, pick the channel in that server's "Channels" tab instead.
- Run
/notices channel purpose: console channel: #console. This applies to all servers. - For a single server:
/notices channel purpose: console channel: #console server: Survival.
Without a channel, the bot posts no console messages, not even in the chat.
Settings
| Where | Setting | Effect |
|---|---|---|
| Config | console.live | false turns the live console off. Default: true. Applies after a restart. |
| "Notices & reports" | "Console warnings" | Turns the messages in the console channel off, for all servers or one |
| Discord | /notices set notice: console enabled: False | The same in Discord |
The "Console" tab is open to anyone with "Manage Server" and to every role with the "Console" right under "Access". Without "Manage Server", each command also needs a grant under "Permissions". See Permissions for details.
Console tools
| Tool | Effect |
|---|---|
| "Add button" | A labeled button for a command you use a lot. Clicking it puts the command into the field; you still send it yourself. Up to 20 per Discord server. |
| "Add schedule" | A command at a set time in your browser's time zone, on chosen weekdays or, with none chosen, every day. "Off" pauses it. Up to 20 per Discord server. |
| "Import commands from CSV" | Runs a list of commands one after the other, one command per line or in the first column. You confirm the list first. |
| "History" | Recently run commands with their output. "Run again" puts one back into the field. |
| Player list | Clicking a name appends it to the command. |
↑ brings back your last command. Buttons, schedules and imports go through commands.mode like a typed command and show up in the command log.
Problems
"There is no live console for this server"
console.live is set to false, or the installed version is too old. Set it to true or install the current version from the download page, then restart the server.
A command is rejected with "Not allowed"
The Minecraft server doesn't accept it. The dashboard shows the two lines to add to the config. Then run /mcsync reload.
"You are not allowed to run this command"
Your role has no grant under "Permissions". An admin can add it there or with /server-command permission add.
"The Minecraft server is not responding"
The connection is down right now. Check under "Connection & chat" whether the plugin checks in.
Nothing arrives in the console channel
- Check with
/notices showthat a console channel is set and "Console warnings" is on. - The bot must be allowed to write in the channel.
- On Paper, only messages that go through Java logging arrive. What a plugin writes straight to Log4j is missing.
Lines are missing in the live console
The server printed more than could be transferred. The full output is in its log file.
Background: why not the whole console in Discord?
A busy server writes hundreds of lines a minute. A channel full of that would be unreadable and would slow down the chat. So only warnings and errors go to Discord, at most 20 lines a minute. When the limit is hit, one line says so. Stack traces stay in the log file; only the exception's class and message go to Discord.
The live console in the dashboard only sends while someone is watching. If you leave the page or click "Stop", the server stops sending within a minute.