Features

Notices

Choose what the bot posts about your Minecraft servers on its own, in which channel, and who gets pinged.

Besides the chat, the bot posts notices about your Minecraft servers: start and stop, lost connections, low TPS, the weekly recap and more. The server has to be connected through chat sync for this. Every setting applies to all servers or to a single one.

Set up

  1. In the dashboard, open "Notices & reports".
  2. Under "Ping role", pick the role that gets mentioned by important notices.
  3. Under "Channels", pick a channel for "Notices" and one for "Reports".
  4. In the "Notices" table, click a cell to change a notice. "All servers" is on the left, each server has its own column to the right.

/notices needs the "Manage Server" permission. Each server's page in the dashboard also has a "Notices" and a "Channels" tab for that server alone.

Settings

Notices

DashboardnoticeDefaultEffect
Server startedserver-startonThe Minecraft server has started.
Server stoppedserver-stoponThe Minecraft server has shut down.
Connectionconnectionon, with pingThe connection to the plugin has been silent for 20 minutes, is back, or never came up. Pings only when it's lost.
Low TPStpsoffTPS below the threshold (15 by default) for more than five minutes.
Delivery problemdeliveryonA reply in the chat when a message from Discord doesn't reach the server. Never pings.
Console warningsconsoleonWarnings and errors from the server console. Only with a console channel, never pings.
Rank role blockedrank-role-blockedon, with pingThe bot can't assign a role from role sync because it's above the bot's own role.
Token leakedtoken-leakedalways onA token showed up publicly and was blocked. Can't be turned off.
Weekly recapweekly-recaponA summary of the week, every Monday.

/notices set takes enabled, ping and, for tps, a threshold between 1 and 20:

/notices set notice: tps enabled: True threshold: 18 server: Survival

Channels

DashboardpurposeContentsWithout a channel
EventseventsJoins, leaves, deaths and advancementsServer's chat
NoticesnoticesStart, stop, connection, TPS and the other noticesServer's chat
ReportsreportsThe weekly recapServer's chat
ConsoleconsoleWarnings and errors from the consoleNot posted
Command logcommandsEvery server command from Discord or the dashboardNot posted
/notices channel purpose: console channel: #server-errors server: Survival

Run it without channel to fall back to the default for that purpose. One channel can serve several servers.

All servers or one

Without server, a setting is the default for all servers. With server: Survival, it applies to that server only. Whatever a server doesn't set itself, it inherits, field by field. reset: True removes a server's own setting again.

In the dashboard, inherited cells are dashed and marked "inherits". /notices show server: Survival marks what that server sets itself with ✏️. The ping role always applies to all servers.

To get notified yourself by email, webhook, push or direct message, see Watch servers.

Update notices

The plugin asks Modrinth whether there's a newer build for your server. If there is, it shows up:

  • in the server log, with a link to the download page,
  • in /mcsync status,
  • in the dashboard under "Connection & chat", with a "Download for this server" button.

Nothing is downloaded or installed. You replace the file yourself. To turn the check off in the plugin:

yaml
# Spigot, Paper, Folia: plugins/mc-sync/config.yml
update:
  mode: off
properties
# Fabric, Quilt, Forge, NeoForge: config/mc-sync.properties
update.mode=off

Problems

No notices arrive

  • The server has to be connected. Without a connection it reports neither start nor stop.
  • Check with /notices show server: Survival whether the notice is on and which channel it goes to.
  • The bot must be allowed to write in the channel ("View Channel" and "Send Messages").

The ping mentions nobody

Without a ping role, a ping mentions nobody. Set it with /notices ping-role role: @Staff. Only notices with ping turned on ping.

Console warnings don't show up

They need their own channel: /notices channel purpose: console channel: #server-errors. Without one, they aren't posted.

A change for all servers has no effect on one server

That server has its own setting for it. Remove it with reset: True, for example /notices set notice: server-stop reset: True server: Survival.

A short outage wasn't reported

A connection only counts as lost after 20 minutes without contact. The bot doesn't report shorter drops.