The free public bots are simply struggling with popularity. So many people are using them that they're getting stuck and taking a long time to do anything, like creating channels or responding to commands.
Sometimes they'll take so long trying to do something that they'll actually just give up and never do it at all.
The only current solutions for this instability are:
Discord has strict rate-limiting that prevents the bot from renaming channels too often. If we consistently hit these limits, the bot would get banned. To prevent this, channels are only checked for renaming once every 10 minutes. More info here
This can happen sometimes around the start of the month, and is typically caused by a declined payment.
If your Patreon payment is declined (e.g. card expired, or you use a temporary/virtual card that doesn't support recurring payments), Patreon instructs AVC that you are no longer an active member, and the bot will stop working for you immediately. Due to the limitted capabilities of Patreon's API, you simply disappear from our system without any notification.
To fix this, simply log into your Patreon account and make sure the payment is made.
It may take up to 3 hours for your membership to reactivate and notify our system that you're back.
If you are certain your payment was made successfully, then also check that your Discord account is still linked to your Patreon account.
Make sure AVC has permissions in the category your channels are in, as well as the specific channels themselves.
Also if you have a Bot role that you give the bot, make sure that has correct permissions too, and take a look at the role hierarchy in your server settings.
If you can't figure it out, you can always give the bot Admin permissions, but this is generally not recommended for any bot, and it is usually possible to get it working without admin permissions, even in complex setups. It just takes a bit of throwing stuff at the wall and seeing what sticks.
To reset your bot permissions, you can try kicking the bot and re-inviting it. It will remember your channel setups, but forget any roles or permissions you gave it.
However, there is one edge case we believe to be caused by a bug in Discord itself. If any role has the Manage Message permission on a category it may break the bots ability to create a new channel. More info about this bug here. The only known workaround to this is to give your bot admin permissions.
We use an older version of the Python library for Discord's API, which does not include soundboard permissions.
Unfortunately newer versions of Discord.py have changed significantly, and it would take a significant rewrite of the bot in order to update to the latest version and thus support soundboard permissions.
If you are interested in working on this, please feel free to make a pull request: https://github.com/gregzaal/Auto-Voice-Channels
Alpha and Beta are the same, these are 2 copies of the same bot in an attempt to spread the load and improve performance.
Alpha is the original "Auto Voice Channels" bot, and is merely referred to as "Alpha" in our support server.
Channel positioning in discord is extremely unpredictable. We do our best and hackiest methods to get it as reliable as possible, but it's not always enough.
If a new channel is going to be the lowest voice channel in your server, it will be placed second from the bottom instead. To work around this, just make an AFK channel, or an invisible voice channel at the bottom of your server.
Channel positioning in discord is extremely unpredictable. We do our best and hackiest methods to get it as reliable as possible, but it's not always enough.
You can try manually moving channels around or deleting them to force the bot's cache to update, which may improve things for you. Otherwise there's nothing anyone can do because the bot already thinks things are correct, discord is simply giving it false information.
No. Private channels are very api-heavy and often hit discord's rate limit as it is. In their current implementation. making private channels by default would get the public bots banned.
This is a highly requested feature though, so it's quite likely we'll have a solution for it in future, but it may be limited to Sapphire patrons and self-hosters only.
This is usually because the bot doesn't have permission to see (or reply in) the channel where you typed the command. Check the bot permissions in these three locations: The server, the category that the channel is in, and the channel itself.
You should see the bot in the user list on the right, though it may still not have permission to send messages there. The most common cause of this is that you're hiding that channel from the everyone role, which includes the bot.
If it's not that, then it's also possible you/someone changed the prefix. Just @mention the bot to test this ("@Auto Voice Channels ping"), and if it responds, then set your prefix back to what you expect it to be (default vc/) with "@Auto Voice Channels prefix vc/".
This is usually because the bot doesn't have permission to see the channel you're looking at. Check the bot permissions in these three locations: The server, the category that the channel is in, and the channel itself.
This is usually because the bot doesn't have permission to create a new channel in that category. Make sure you add the bot's role to that category's permissions and enable the following:
This is usually caused by hosting the bot on a poor internet connection, such as your home network. Every "Ready" message indicates the bot lost connection and then reconnected.
We recommend using a cheap VPS as these are usually located in a datacenter with a stable internet connection, but you can also set "disable_ready_message": true in your config file.