Custom Commands Not Working

If your custom command isn’t working, check these:

1. The command is disabled

Make sure:

• Custom Commands are enabled globally

• The specific command is enabled

2. The trigger is incorrect

• Triggers cannot contain spaces

• Make sure you're using the correct prefix, and prefix commands are enabled

• Commands are case-sensitive depending on your setup

• %rules might work, but %Rules might not

3. No actions are configured

A command with no actions will do nothing.

4. Cooldown is blocking usage

If a cooldown is set, the command may appear to not work when it’s actually just waiting.

5. Missing permissions

Some actions require permissions:

• Delete Message: Manage Messages
• Give/Remove Role: Manage Roles
• Set Nickname: Manage Nicknames

Also ensure:

• The bot’s role is above the target role
• The bot can see and send messages in the channel

6. Role hierarchy issues

If roles aren’t being assigned, Axis must be higher than the role it’s trying to give/remove.

7. Another bot is conflicting

If multiple bots use the same prefix and command, or another bot deletes Axis' response, they may conflict with each other.

Try changing Axis' prefix or the command trigger, or prevent other bots from removing Axis' messages.

Tip: You can check if this is happening in your Servers audit log.

8. Command limit reached

• Max 100 commands
• Max 5 actions per command

Still not working?

Try:

• Re-saving the command
• Disabling and re-enabling it
• Testing in a different channel

If everything looks correct and it still fails, it may be a bug. Join our support server, and tell us:

• Command trigger
• Actions configured
• What you expected vs what happened