-
Notifications
You must be signed in to change notification settings - Fork 50
Common Issues
Before posting any issue, you need to follow one of these rules or the issue will be considered invalid and will be closed:
- if you found a bug, describe what kind of bug you found and if possible, attach some screens to the comment with some examples and tests;
- if you propose a solution to fix buggy code, open a pull request so I can see the complete code and approve the solution. I also need to know why you are making a particular change and why it is better than the current solution in the code. If you do not open a pull request the solution will not be considered;
- do not open an issue about a simple question when you can google it and find the answer in a matter of seconds. For example What is CX ?.
Here are some common issues and workarounds:
The google command is not 100% correct, if you do a search query the first result will be correct, but from second above the googleResults.json will corrupt itself. This simply means you will get a wrong query.
First of all, check if you have installed FFmpeg and the node modules. If everything is correct but the bot is still not playing the music, open the cmd or terminal and navigate to the root of your repository and type npm update ytdl-core, which is the only package that needs to be updated regularly.
There is a Bitrate setting on each voice channel which is defaulted to 64kbps. Click the gear sign next to the voice channel to go to the channel settings and make sure your Bitrate is as high as it will allow. According to GitHub issues on other repositories, Discord channels can reach 96kbps and partnered discord servers can be set up to 128kbps. The music quality also depends from the connection.