-
Notifications
You must be signed in to change notification settings - Fork 1
Troubleshooting
Cyrusbye720 edited this page Jun 6, 2026
·
3 revisions
- Check the token in
config.ymlis correct. Tokens look likeMTI...and are about 70 characters long. - Check the Message Content and Server Members intents are enabled on the bot in the Discord developer portal.
- Check
bot.guild-idmatches your server ID. The slash commands will not register if the bot is not in the guild. - Look for "Failed to connect to Discord" in the server console; the underlying error is usually printed.
- ZDiscord registers commands with the configured guild immediately. If the commands still do not appear, run
/zdiscord reloadin-game. - The bot needs the
applications.commandsOAuth scope to register slash commands.
- The bot needs the Manage Webhooks permission in
channels.chat. - If the existing
ZChatwebhook is deleted, the next message will recreate it. - The console will log "Failed to create webhook for #channel-name: ..." if the create fails.
If the embed message is posted twice, delete one of them and clear channels.status-message in config.yml. The next update will post a new message and write the new ID.
The threshold is the number of unbypassed players in a sliding time-window. Increase anti-raid.max-joins or decrease anti-raid.time-window to taste. Players with zdiscord.bypass.antiraid are not counted.
On Spigot, Bukkit.getTPS() is unavailable and the embed shows 20.0 / 20.0 / 20.0. Switch to Paper if you need real TPS data.
Codes are valid for five minutes. Run /zdiscord link again to generate a new one.
ZDiscord logs a warning and falls back to YAML for the lifetime of the process. Common causes:
- The MySQL server is not running or is unreachable. Check the host and port.
- The credentials are wrong. The default user is
rootwith an empty password, which is rarely correct outside of a local development setup. - The database does not exist. Create it with
CREATE DATABASE zdiscord;and restart.