Bot is not ready or author not in voice channel, please try again later. #27
Assignees
Labels
question
Further information is requested
Comments
Everything looks like it's setup correctly, those parameters are also good. The type errors are expected for empty environment variables. So 1st troubleshooting step would be to verify that you are connected to a voice channel that the bot is allowed to be in. You can check that in your channel settings. The bot should have a role in there with the same name. Here's a few prerequisites that the bot looks for (some of these I'm working on loosening in the future but haven't had a chance to fix it just yet). 1)The bot assumes you are connected to a voice channel when using the /play command. 2) it assumes that you have given it permission to be in same the channel as you. 3) it assumes that you have a connection to ABS. 2nd is to make sure you have full intents enabled in the bot dev portal enabled. I'm going to look into your logs a bit more before concluding anything. Try these and if it works then awesome. |
|
I'm not entirely certain how I fixed it, but I did. I created a new server and added the bot to it - I also gave it a bunch of permissions in the dev portal, most of which I'm fairly certain were unnessessary. It may have also been that the original server was misconfigured in some way. |
|
Just skimmed through everything and I don't think you're running into any errors on the server side (whats running the bot) looks to be a permission issue or a client issue (need to reload discord). The context behind this is the first check is this (there is other error checking but thats long and tedious and wont get into that) |
|
Pinning this for future peeps in case they run into something similar. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm trying to use this bot, but I keep getting the same message.
The logs seem to indicate that it's correctly connected to abs, and the autocomplete and suggestions appear to work correctly.
Maybe I've set something up incorrectly?
In the docker run command I had to use
as the container logs would complain that they weren't strings.
The text was updated successfully, but these errors were encountered: