Slash commands don't show up

Possible causes

• The bot was invited without the applications.commands scope.
• Discord hasn't finished syncing the commands to your client yet.
• Your role, or the bot's role, doesn't have permission to use slash commands in that channel.
• The bot is down or restarting.
• Discord's cache is corrupted.

Quick fixes

1. Check that the bot is online

First of all, look at the member list and see whether Roody shows up in green. If it's red or grey, wait a few minutes: the bot may be restarting after a deploy. You can check the status in real time on the Service status page.

2. Restart the Discord client

Discord caches the slash command list in each client. Forcing a restart is usually enough:

• Desktop: press Ctrl+R to refresh (or Cmd+R on macOS). If that doesn't work, close Discord completely from the system tray and open it again.
• Mobile: close the app from the task switcher and open it again.
• Web: reload with Ctrl+F5 (or Cmd+Shift+R on macOS).

3. Check the "Use Application Commands" permission

Even with the bot in the server, Discord can hide its commands if the bot's role — or yours — doesn't have permission to use them in that channel:

1. Open Server Settings → Integrations.
2. Click on Roody and check the "Commands" section.
3. Confirm that your role (or @everyone) has access to the commands in the channel you're typing in.

4. Wait for the sync

When a command is added or updated, Discord can take:

• A few seconds on small servers and for server commands.
• Up to 1 hour for global commands on accounts with a huge number of servers.

If you've just invited the bot, wait at least 5 minutes before assuming something is wrong.

Advanced fixes

Re-invite the bot with the right scope

If you invited Roody with an old URL that didn't include applications.commands, the slash commands will never register. You'll have to invite it again:

1. Always use the official link from How to invite Roody.
2. You don't need to kick the bot first; accepting the link again forces the missing scope to be granted.
3. Your dashboard settings are kept.

Clear Discord's cache

As a last resort on desktop:

1. Close Discord completely.
2. Press Win+R and type %appdata%/discord (on macOS: ~/Library/Application Support/discord).
3. Delete the Cache, Code Cache and GPUCache folders.
4. Open Discord again.

Checklist

If nothing works

Contact support with these details to speed up the diagnosis:

• The server ID.
• When the commands stopped appearing.
• Which of the steps above you've already tried.
• A screenshot of the menu when you type /.

Related links

• How to invite Roody
• Permission problems
• The bot isn't responding
• Contact technical support