What exactly is your problem?
- Roody shows as offline (grey in the member list) → keep reading below.
- The commands don't appear when you type / → go to Slash commands don't show up.
- They appear but the command returns an error → go to Commands that fail.
- It's a permissions problem → go to Permission problems.
This article covers the case where the bot is online but doesn't reply at all, or shows as offline.
1. Check the bot's status
- Look at the server's member list:
- Green → online and connected.
- Grey → offline or still loading.
- If it's offline, check the Service status page: major incidents show up there.
- If the bot was just invited, give it a couple of minutes: Discord takes a while to propagate the connection.
2. Try a basic command
Run /serverinfo in a channel where the bot can write:
- If it replies, the bot works and the problem is specific to the command or channel you were using.
- If Discord shows "The application is thinking…" for 15 seconds and then nothing, move on to the next step.
- If it doesn't even show that, the bot is probably down or has no permissions in the channel.
3. Check the channel's permissions
The bot may be online but unable to read or write in the channel you're talking to it in. Check:
- View Channel
- Send Messages
- Use Application Commands
- Embed Links (most replies are embeds)
Check this under Edit Channel → Permissions, making sure Roody's role (or @everyone) has these permissions enabled for that channel.
4. Restart the Discord client
Sometimes it's something as silly as a broken local connection:
- Desktop: Ctrl+R to refresh. If that doesn't help, close Discord completely and open it again.
- Mobile: close the app from the task switcher.
- Web: reload with Ctrl+F5.
5. Check the server's verification level and filters
Aggressive server settings can block the bot:
- Under Server Settings → Moderation, check the verification level. If it's very high, the bot may not be able to talk until its account meets the requirements.
- Check that the bot isn't in timeout (a clock icon in the member list). If it is, lift it from the context menu.
- Check that no word filter on the server itself is deleting the bot's replies.
6. Check that no other bot is intercepting
If you have another bot with a command of the same name (say, two bots with /ban), Discord runs whichever one you picked in the dropdown. When you type /, look at which bot the command is assigned to.
7. Re-invite the bot
If none of the above works, re-invite Roody with the official link. You don't need to kick it first; the new invite will add any missing permissions and scopes. Your dashboard configuration is kept. See How to invite Roody.
Checklist
If nothing works
Contact support with:
- The server ID.
- The approximate time of the attempt (with time zone).
- Screenshots of the channel where it isn't responding and of the permissions tab.
- Which of the steps above you've already tried.
Comments
Share your experience or ask anything about this article.
Join the conversation
Sign in to leave comments and take part in the conversation.
Sign in