Skip to main content

Troubleshooting

Having issues with NeatQueue? This guide covers common errors and their solutions.

Permissions Errors​

The most common issue with NeatQueue is permissions-related errors.

Symptoms​

  • Bot fails to create channels
  • Cannot send messages in certain channels
  • Unable to manage voice channels
  • Missing reactions or buttons

Solutions​

Check these permission requirements:

  1. Required Bot Permissions

    • Send Messages
    • Embed Links
    • Manage Channels
    • Manage Roles (if using role features)
    • Connect (voice)
    • Move Members (voice)
    • View Channel

  2. Role Hierarchy

    • Ensure the bot's role is high enough in the role list
    • Bot roles must be above any roles it needs to assign
    • Bot cannot manage users with higher roles

  3. Channel-Specific Permissions

    • Check individual channel permissions
    • If a category or channel is private, add the bot explicitly
    • Category permissions override server permissions

  4. Permission Overwrites

    • A custom role for the bot shouldn't have "Deny" permissions
    • Channel permission overrides can block the bot

Quick Fix​

Fast Solution

If you're unsure about permissions, temporarily give the bot Administrator permissions to verify it works. Once confirmed, you can scale back to specific permissions.

Note: This is not recommended for production use, but helps diagnose permission issues.

Detailed Permission Check​

  1. Go to Server Settings → Roles

  2. Find the NeatQueue bot role

  3. Verify it has these permissions:

    ✓ View Channels
    ✓ Send Messages
    ✓ Embed Links
    ✓ Attach Files
    ✓ Read Message History
    ✓ Add Reactions
    ✓ Manage Channels
    ✓ Manage Messages
    ✓ Connect
    ✓ Speak
    ✓ Move Members

  4. Check channel-specific overrides:

    • Right-click the queue channel
    • Go to "Edit Channel" → Permissions
    • Ensure NeatQueue has green checkmarks (not red X's)

Stats Not Updating​

Players Not Appearing on Leaderboard​

Common causes:

  1. Required games not met

    • Check: /leaderboardconfig requiredgames
    • Default: 1 game required
    • Fix: Lower requirement or wait for more matches

  2. Wrong stats linked

    • Check: /info → view stats configuration
    • Fix: /leaderboardconfig sharedstats set name:<old name> to point the queue back at its stats
    • Common trigger: renaming a queue, or toggling /leaderboardconfig sharedstats serverwide off. The data is not gone — the queue is reading an empty name. See Stats Linking and Migration

Stats Reset Accidentally​

danger

Stats resets are permanent and cannot be undone by the bot.

Prevention:

  • Double-check before running /managestats reset
  • Keep screenshots of important leaderboards
  • Use /managestats copy before experimenting

Recovery:

  • Manual restoration is not possible
  • You'll need to rebuild stats from scratch

MMR Issues​

MMR Changes Seem Wrong​

Understanding MMR variance:

MMR changes vary based on team balance. A win against a higher-rated team gives more MMR.

To make MMR static:

/mmr change set static:true

This makes all wins/losses change MMR by exactly the same amount.

Slash Commands Not Appearing​

Possible causes:

  1. Bot recently added

    • Can take a few minutes for commands to register
    • Fix: Wait 5-10 minutes, restart Discord app

  2. Permissions

    • Bot needs "Use Application Commands" permission
    • Fix: Check bot permissions

Getting Additional Help​

If you've tried these solutions and still have issues:

  1. Check bot status

  2. Join support server

    • Get invite from bot profile or website
    • Support team and community can help

  3. Provide details when asking for help

    • What command you ran
    • What error message appeared (screenshot if possible)
    • What you expected to happen
    • Server ID and channel ID (if relevant)
Pro Tip

Before asking for help, try:

  1. Run /info to see your queue configuration
  2. Check bot permissions in server and channel settings
  3. Try in /test mode to isolate the issue
  4. Check if the issue happens in a fresh channel