FAQ & Troubleshooting

We’ve tried to make our onboarding process as simple as possible - with our setup guide and fully documented list of bot commands - but sometimes, things don’t go to plan, and you get stuck.

Discord server administration gets ever more cumbersome as time goes by and as communities grow, and we’ve tried to take that into account.

Coverage Bot sets up its own roles and channels to work completely independently of your existing server structure - it doesn’t interfere or clash in any way, so it’s good for the long haul.

The following is a list of frequently asked questions, as well as other tips for troubleshooting your installation.

Pricing?

• What if I go above the coverage limit on my plan? Firstly, congrats! Your game is a great success! (1,000 streams in a month is pretty good!) Secondly, that’s no problem at all. If it happens more than once, we’ll reach out. The usual solution is to stack two of the same subscription plan - e.g. it works the same as adding an extra game - but also consider the next plan up!

I’ve installed it to my Discord Server, but it doesn’t work?

• Do you have a valid and active Coverage Bot subscription? If not, it won’t work! Sorry! Visit the Dashboard page to setup a subscription.

• Do you have “2FA Moderation” enabled on your server and account? This is a necessary part of the setup process, and must be enabled before the bot can do anything in your server. This is mandated by the Discord platform for security purposes. You can find this in “Server Settings” > “Moderation/Safety Setup” > “Permissions” > “Require 2FA for moderator actions”

• I don’t seem to have permissions to install the bot? You must have Administrator or Manage Guild roles/permissions to install a bot to your server.

• Are the channels and roles there in your server? If not, it’s likely the bot doesn’t have enough permissions to create them. Move the role to the top of the role list, and then send a /init message in chat to prompt the bot to retry.

• The role looks correct - near the top - but no role or channel was made when I sent /init? Coverage Bot cannot initiate if it cannot view the channel you send the message in. Make sure you can see the bot in the member list.

It was working before, but now it’s not?

• Did you change/sync permissions on the #coverage-moderation channel? If the bot cannot view this channel then it’s moderation features will cease to work.

• Did you change the Coverage Bot (Moderator) role? If your user does not have this role or the Manage Guild/admin role, you won’t be able to view the moderation channel.

• Did you kick the bot and re-join it? This shouldn’t affect the bot, but you never know! Make sure roles and channel permissions are correct.

• Did you remove its role? This shouldn’t be possible…

Why does it need all those permissions?!

• Manage Channels: It creates a #coverage-moderation channel on your server. This is a safe place for you to approve/reject potential coverage in, outside of the public eye. Only members with the Coverage Bot (Moderator) role can view this channel, as below.

• Manage Roles: It creates a Coverage Bot (Moderator) role on your server. This role is for people who can view the #coverage-moderation channel.

• Send/Read Messages & Embed Links: It sends you coverage notification messages!

• Manage Messages & Manage Emojis: The moderation queue system uses emojis to let you approve/reject without typing in text commands for each item. It’s much quicker!

Got another question?

That’s all we’ve been asked so far - but we’re aware there may be gaps in knowledge. Let us know if you have a question that we’ve missed.

We’ll update this page with any new questions/requests. We’re always happy to help! ✅