Troubleshooting
Solutions to common problems
Last updated
Was this helpful?
Solutions to common problems
Last updated
Was this helpful?
This page contains solutions to common issues. If this page doesn't help you,
Starting at the end of August 2022, Discord will only allow bot commands to be called by slash commands. Slash Commands
To respond to commands, Eventcord requires the following permissions in the channel you are sending the commands:
Read messages
Send messages
Use embeds
Without these three permissions, Eventcord can't respond to you at all. Eventcord also has other recommended permissions which can be seen in the . Additionally, Eventcord does not support threads currently. Use a text channel or a voice chat for commands.
This is likely due to a permissions issue. First, make sure the bot has the manage roles permission. Then, make sure the bot's role is listed above the reward roles in your server's role hierarchy.
Eventcord uses a role to figure out who has permission to start, stop, or manage a queue. Eventcord checks whether a member has the role based on the name of the role. By default, the role Eventcord looks for is a role named "Event Admin" (case sensitive). You can customize the role which Eventcord looks for by using the /setup command or by using the /config command (see ). If you need help creating roles, check out . If you need help managing roles, check out . For help getting started with Eventcord or customizing Eventcord, check out these pages:
Wait a few seconds. If you continue to receive this error for seemingly no reason, join our
Be sure to check you are using the correct prefix. If you are, there is always the possibility that Eventcord or a service Eventcord uses has experienced a fatal error. If the bot doesn't come back online within a few minutes, .
If you couldn't find what you are looking for, you can get help on .
Your server may have been blacklisted for Eventcord's safety. for help with this.
