Skip to main content

Troubleshooting Guide

This guide provides solutions to common issues users might encounter when using the bot. Follow these steps to quickly resolve errors related to permissions, command usage, or configuration.

Common Issues and Solutions​

1. Missing User Permissions​

Problem​

The user tries to execute a command but receives an error indicating they lack the required permissions.

Solution​

  • Check if you have the necessary permissions to run the command. For example:
    • Manage Server: Required for moderation commands.
    • Administrator: Required for high-level commands.
  • If you don't have the required permissions:
    • Contact your server administrator to grant them.
    • Confirm that the bot is configured correctly to recognize your roles.

How to Check Permissions​

  • Right-click your username in the server and select Roles.
  • Verify that you have the appropriate role(s) with the required permissions.

2. Missing Bot Permissions​

Problem​

The bot cannot execute a command or send messages due to missing permissions.

Solution​

  • Ensure the bot has the following essential permissions:
    • Send Messages
    • Embed Links
    • Manage Roles (for commands involving role assignments)
    • Use Slash Commands
  • If the bot lacks permissions:
    1. Go to Server Settings > Roles > [Bot Role].
    2. Verify the necessary permissions are enabled.
    3. Drag the bot's role above roles it needs to manage (e.g., reaction roles).

Example​

For a reaction role command:

  • The bot’s role must be higher in the role hierarchy than the roles it is assigning.

3. Command Errors​

Problem​

Commands fail to execute or return unexpected errors.

Solution​

  1. Syntax Check:
    • Double-check the command syntax. Refer to the documentation for correct usage.
  2. Check Required Options:
    • Ensure all required fields are provided.
    • Example: /reaction-roles button create requires at least role-1 to be specified.
  3. Cooldowns:
    • Some commands may have cooldowns to prevent spam. Wait a few seconds and try again.
  4. Missing translations
    • Some commands may be translated improperly. Try setting the bot language to English by using /language set [language:English] before trying again.

4. Bot Not Responding​

Problem​

The bot does not respond to commands or is offline.

Solution​

  1. Check Bot Status:
    • Confirm the bot is online in your server’s member list.
    • If it’s offline, check the bot's support server or website for updates.
  2. Reinvite the Bot:
    • Use the /invite command to get the latest invite link and ensure permissions are granted during setup.
  3. Slash Command Setup:
    • If slash commands are missing:
      • Go to Server Settings > Integrations > Bot and verify command permissions.

5. Issues with Reaction Roles​

Problem​

Reaction roles do not function as expected.

Solution​

  • Ensure the bot's role is higher than the roles being assigned.
  • Verify the bot has the Manage Roles permission.
  • Confirm the command syntax and ensure the roles exist in the server.
  • Remember: A single reaction role command supports a maximum of five roles per row. Use multiple commands for additional roles.

6. Language or Translation Issues​

Problem​

The bot's responses or embeds display incorrect or missing translations.

Solution​

  • Check the server's language settings:
    • Use the appropriate command to set the desired language.
  • If a translation is missing, report the issue via /feedback.

7. Interaction Timeout​

Problem​

You started a command requiring input but didn’t respond in time.

Solution​

  • Commands with modals (like /feedback) have a timeout of 5 minutes.
  • Restart the command and complete the input promptly.

8. Reporting Bugs​

Problem​

You’ve encountered an unexpected bug or error.

Solution​

  • Use the /feedback command to report the issue.
  • Provide the following information:
    • What you were trying to do.
    • Any error messages you received.
    • Steps to reproduce the issue.

9. Deleting All Data (Last Resort Method)​

Problem​

The bot is malfunctioning, or there’s a significant issue with the server's data that cannot be resolved. In this case, you may want to reset everything to start fresh.

Solution​

To completely reset the server's data, use the following command:

/data delete all

This will delete all the data associated with your server from the database, which includes invite information, role assignments, and other bot-specific configurations. Warning: This action is irreversible.

Steps:

  1. The bot will ask for confirmation before proceeding with this action.
  2. You will be prompted with buttons to confirm or discard the deletion.

How this helps:

  • If something breaks and the bot is malfunctioning or is unable to function as expected, running this command will reset everything.
  • After the reset, you can simply reinvite the bot to the server and set it up again as if you were starting fresh, eliminating any issues that may have been caused by corrupted data.

Preventing Issues​

  • Ensure the bot's role has all necessary permissions when inviting it to your server.
  • Regularly check for updates or announcements in the bot's support server.
  • Train server moderators on how to use key bot commands effectively.

By following this guide, most issues can be resolved quickly and easily. If problems persist, feel free to reach out via the bot's support server or feedback command.