Solutions to common problems
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 FAQ. Additionally, Eventcord does not support threads currently. Use a text channel or a voice chat for commands.
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 changing roles). If you need help creating roles, check out this Discord article. If you need help managing roles, check out Role Management 101. For help getting started with Eventcord or customizing Eventcord, check out these pages:
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.
Video showing how to fix role hierarchy issues. The bot's role is being placed above the reward roles.
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, please report the issue on our Discord server.