Skip to content

Troubleshooting

Siam Islam edited this page Jul 5, 2026 · 3 revisions

Bot shows offline in Discord, no error in console

  • Check your internet connection. If DNS lookups are failing on your machine, JDA cannot reach Discord's servers.
  • Confirm the bot token is correct. A wrong token throws an error at startup and disables the plugin, check your console log for that.

Messages not relaying from Discord to Minecraft

  • Confirm Message Content Intent is enabled in the Discord Developer Portal, under the Bot tab. Without it, the bot receives blank message content with no error.
  • Confirm the channel ID in config matches the channel you're actually typing in.

Config changes not taking effect

  • If you edited the config file inside your project's source folder (src/main/resources/config.yml), that is the template, not the live file. The server reads from its own deployed copy, usually under plugins/DiscordPulse/config.yml on a real server, or a similar path inside your test server folder if you're using Gradle's run-paper.
  • Editing the source template does nothing until you rebuild and the deployed file doesn't already exist. If the deployed file already exists, it will not be overwritten automatically.
  • Fix: either delete the deployed config and restart to regenerate it, or manually edit the deployed copy directly.

Playerlist command not deleting messages

  • The bot needs the "Manage Messages" permission in that Discord channel. If it was invited without this permission, message deletion fails silently, no error shown.
  • Check the bot's role permissions in your Discord server settings.

Build fails with a shadowJar error mentioning "StubbedFileCopyDetails" or "No such property: mode"

  • This is a known incompatibility between older Shadow plugin versions and newer Gradle versions.
  • Fix: use com.gradleup.shadow version 8.3.5 or newer in build.gradle.kts, not the older com.github.johnrengelman.shadow.

Server shows a warning about running an outdated Paper build

  • This plugin is built and tested against Paper 1.21.11 specifically. Paper has since moved to a new versioning scheme (26.1.x and beyond). This plugin has not been tested past 1.21.11, expect possible breakage on newer versions.

Still stuck

Open an issue on the GitHub repo with your exact error message from console, not a paraphrase. Paraphrased errors hide the actual cause.