Skip to main content
Filter your server console for [nexdev_queue] — most issues print a clear error there. If you’re not sure, flip Config.Server.DebugMode = true temporarily, restart, and try again.

Common issues

Diagnostic checklist

If something’s not working, walk through this in order:
  1. Is the resource started? ensure nexdev_queue should be in server.cfg and you should see a [nexdev_queue] Boot OK line on boot.
  2. Is the bot online in your guild? If it’s offline, the token is wrong.
  3. Is Server Members Intent ON? In the Developer Portal → Bot page.
  4. Are the IDs right? Guild ID, channel ID, role IDs — all are 17–19 digit numbers, copied with Developer Mode in Discord.
  5. Did you restart the resource after editing the config? Most settings need a restart. (Themes don’t — see Themes.)
  6. Is DebugMode on? Turn it on for the test, off again in production.

Before opening a support ticket

Please include:
  1. The behavior you’re seeing vs. what you expected.
  2. Whether the bot shows online in your Discord.
  3. The [nexdev_queue] lines from your server console (with DebugMode on).
  4. Your Config.Server block with the token redacted (replace it with ***).
  5. Whether you have another queue resource running.
See Support & contact for how to reach us. Never paste your bot token in a ticket — redact it first.