Commands aren't working

Identify the type of error

Roody returns very different messages depending on the cause. Work out which is yours:

• "You don't have permission to use this command" → it's failing because of your role.
• "I'm missing permissions to do this" → it's failing because of the bot's role.
• "This module is disabled" → it's failing because of the dashboard configuration.
• "You haven't configured [X]" → a channel/role the module requires is missing.
• "Command only available to premium" → the command requires Roody Pro/Team.
• Roody thinks but replies with nothing → a possible bug, or a temporary outage of an external service.
• A generic Discord error ("The application did not respond") → the bot took too long, or was down when it ran.

1. "You don't have permission to use this command"

1. Check which role the command requires. For moderation, it usually matches Discord's native permissions (ban, kick, manage messages…).
2. Ask an administrator to assign you the matching role, or to enable your role in the module from the dashboard.
3. If the command belongs to a specific module (tickets, suggestions, levels), check that module's Allowed roles section.

2. "I'm missing permissions to do this"

1. Look at which permission the message mentions (e.g. "I need Manage Channels").
2. Go to Server Settings → Roles → Roody's role and enable it.
3. If the command acts on a user with a role above Roody's, move the bot's role above the target user (hierarchy).
4. If it's a per-channel permission, check the overrides on the channel you're running the command in.

More detail in Permission problems.

3. "This module is disabled"

1. Open /dashboard and select your server.
2. Go into the relevant module (economy, levels, tickets…).
3. Turn on the module's main switch and save.
4. Try the command again.

4. "You haven't configured [X]"

Some modules need a channel, role or category before they can work. Typical examples:

• Tickets: the panel channel, the log channel, the category or the staff roles are missing.
• Suggestions: the channel they're posted in is missing.
• Welcome/goodbye: the announcement channel is missing.
• Logs: the specific event has no channel assigned.

Go into the module from the dashboard, fill in what's missing and save.

5. Premium command

Some advanced commands are reserved for the Roody Pro and Roody Team plans. If you need to use one, check the server's plan from the dashboard. The free version will keep working for everything essential.

6. Roody thinks but doesn't reply

Discord shows "The application is thinking…" for several seconds and then nothing, or "The application did not respond" pops up:

1. Check the bot's status on Service status. If there's an incident, wait for it to be resolved.
2. If the command depends on an external service (music, translator, anime, Pokémon), the provider may have a temporary outage; try again in a few minutes.
3. Retry once only. Firing the same command several times in a row doesn't speed anything up and may trigger a cooldown.

7. "You're on cooldown"

Many commands (economy ones especially: /work, /fishing pescar, /steal user) have a waiting time between uses. Wait for the time shown in the reply.

8. Economy commands showing the wrong balance

• If you think your balance is wrong, compare it with /balance. The dashboard can take a few seconds to reflect the last transaction.
• If you buy an item with an associated role and it isn't applied, check that the bot's role sits above the role it hands out.

9. Ticket commands that don't open a channel

• It's usually the bot missing permissions on the category: it needs Manage Channels and Manage Permissions on the category, not just on each child channel.
• Check the server's channel limit (Discord caps it at 500).
• If maintenance mode is on, users won't be able to open new tickets until you turn it off with /maintenance.

Quick checklist

If none of this adds up

Contact support with:

• The exact command you ran (with its parameters).
• The literal error message Roody returns.
• The server ID and, if possible, the affected user's ID.
• The approximate time of the attempt (to correlate with logs).

Related links

• Slash commands don't show up
• The bot isn't responding
• Permission problems
• Contact technical support