Skip to main content

Slash Commands Not Working

MEE6 slash commands not working on your Discord server? Follow this step-by-step troubleshooting guide to diagnose and fix the issue.

Follow the steps below to solve any issues with your slash commands.

You need to try these steps one-by-one, checking after every step if the issue is resolved or not:

  1. Check if the command in question is enabled on your server's dashboard. Try turning it off and back on again.

    Using Bot Maker modules? Discord allows each bot a maximum of 100 slash commands per server, and MEE6's own commands can already use most of them. If your modules push the total over 100, Discord rejects the whole command update: new or renamed commands won't appear, and some old ones can stay in the list but stop working. A typical sign is that turning a plugin off seems to fix it, and turning it back on breaks it again.

    To get back under the limit, you can either:

    • Turn off the MEE6 commands or plugins you don't use on your Dashboard. Each disabled command frees up one slot.

    • Ask the Bot Maker AI to group your module's commands under one parent command (for example /fish cast and /fish sell instead of /cast and /sell), then deploy again. A grouped command only counts once toward the limit.

  2. Check that members (who can't see the command) or one of their roles roles have the Use application commands permission, globally on the whole server or in that particular channel.

  3. Make sure that the settings and permissions for the command in question are correct. Follow our How to Set Role Permissions for MEE6 Commands support article for a step-by-step guide.

    Try adjusting them slightly → Save → Adjust back → Save.
    ​

  4. Press the Re-sync now button your server's dashboard → Settings and follow any instructions it displays. This function syncs command permissions between the MEE6 dashboard and Discord Integrations.
    Depending on the server configuration it will do one of the following:

    1. Do the sync right away.

    2. Show a pop-up to authorize access to command changes.

    3. Will ask to re-authorize the custom bot (see the step #6 below).

  5. If you have only MEE6 and no custom bot (Bot Personalizer), try kicking MEE6 from your server and inviting it again. All your information will be saved. Wait ~5 minutes for slash commands to appear again for the bot.

  6. If you have a custom bot (Bot Personalizer), and if you are the person who owns the custom bot, then kick your custom bot.

    All your information will be saved.

    Then, go to https://discord.com/developers/applications and select your application.

    1. Go to the Bot tab, scroll down to Privileged Gateway Intents, and make sure Presence Intent, Server Members Intent, and Message Content Intent are all enabled. Do NOT enable "Requires OAuth2 Code Grant".

    2. Go to the OAuth2 tab, in the Redirects section, press "Add Redirect" and enter https://mee6.xyz/custom-bot-auth. Click outside the field to trigger the save prompt, then press "Save Changes".

    3. Still on the OAuth2 tab, press "Reset Secret" to generate a new Client Secret. Copy it and save it temporarily.

    4. Go to the Bot tab and press "Reset Token" (or "Click to Reveal Token") to get your Bot Token. Confirm the modal and copy the token.

    5. Go to your MEE6 Dashboard → Invite MEE6 if needed → Your server → Bot Personalizer. Check the 3 confirmation checkboxes, paste in your Client Secret and Bot Token, and press "Enable Bot Personalizer".

    6. Authorize the bot and command permissions in the 2 consecutive Discord pop-up windows that appear. If no pop-up shows, make sure your browser isn't blocking pop-ups.

    Keep in mind that if your server has 2FA (check via Server Settings → Moderation → Safety Setup → Permissions), you will need 2FA enabled on the Discord account owning the custom bot as well.

    Once authorized, make sure to bring the custom bot to the top of the role list (Server Settings → Roles) so it can operate fully.

    Lastly, follow step #4 again to make sure that the role permissions are set correctly. Integrations settings should be synced automatically, but it's helpful to check.

  7. If the previous steps didn't help, wait 24 hours and see if the commands are back on the server and if they work or not. Discord has rate limits on the number of commands that can be activated per 24 hours.

If you have any questions about this, do not hesitate to join our Support Server✌️

Did this answer your question?