❓
FAQ
Frequently Asked Questions.
There are four main reasons to why you received this message:
1. InviteManager cannot see the channel to which the invitation is directed. (Permission issues can be easily solved by granting the administrator role to InviteManager).
2. Multiple people joined at the same time.
3. The invites made are not being registered by discord.
4: The bot has just restarted, and the invitation from your server was not in the InviteManager internal cache at the time. This is only temporary.
This should only happen once after the bot restarts.
Fakes invites mean that the bot count members who joined under the minimum account age set using
/fakedelay command.You can vote for InviteManager on top.gg, click here to access our page. Thank you, voting really help us out!
Every roles you want InviteManager to give must be under the bot's role. You also need to make sure that the bot has the permission to grant roles.
Permission | Usage |
Add Reactions | |
Attach Files | |
Manage Messages | |
Manage Roles | |
Manage Server | Viewing the server's active invites so InviteManager can track them |
Manage Channels | Listen to new invites created or deleted on your server |
Read Message History | |
Send Messages | |
Use External Emojis | Use private emojis in most InviteManager command responses |
Ban Members | Only needed when using action type ban at verification system, used to make the action of ban the member |
Kick Members | Only needed when using action type kick at verification system, used to make the action of kick the member |
All required permissions for InviteManager are required for some reason, so please be careful about which permissions you remove. If you remove permissions, it is likely to make some features of InviteManager non-functional.
Last modified 5mo ago