OriusBot does not answer my commands

TroubleshootingCommands

You type a command and nothing happens, or Discord writes “The application did not respond”. Go through the checks below in order.

1. Is the bot present and online?

  1. Open your server’s member list If the list is hidden, click the “people” icon at the top right of Discord.
  2. Look for OriusBot It must be in the list with the BOT tag and a green dot (online).

Missing? It was not added or was kicked: see How do I add OriusBot to my Discord server? Present but greyed out (offline)? Wait a few minutes and retry; if it lasts, tell support.

2. Are you typing it as a Discord command?

OriusBot commands start with /. Type / in the message box: Discord opens a list. Click the command in the list instead of typing it all out as text. If the command does not appear in the list, go to step 3.

3. Are you allowed to use it in this channel?

  1. Check the channel An administrator may have limited some commands to certain channels or roles. Try another channel.
  2. Check the panel Open the panel, Configuration menu then Commands: the command may be disabled there.
  3. Check your Discord permissions Some moderation commands require a permission (for example Ban Members). Without it, Discord hides the command.

4. Can the bot write in the channel?

Right-click the channel, Edit Channel, Permissions. OriusBot’s role must be able to View Channel, Send Messages and Embed Links. If one of these is denied, the bot answers into the void.

5. Still nothing?

Note the exact time, the channel, the command typed and Discord’s message, then contact support with those four items: they let us trace your request.

Do not remove the bot’s permissions Removing a permission from OriusBot’s role silently disables the features that depend on it. If in doubt, restore the original permissions rather than adding some at random.

Still stuck?

Contact support with the title of this article, the step where you are stuck and what you see on screen.

Contact support More articles: Troubleshooting

Last checked: 13 November 2026.