Eek! A bug? (o´･_･)っ

Sometimes things don't go as planned. Here are some common problems and their solutions.

Problem: The bot is online, but slash commands don't appear in my server.

• Solution: You might not have invited the bot correctly. When you invite the bot to your server, make sure the applications.commands scope is checked. You may need to kick the bot and re-invite it using the correct invite link from the Discord Developer Portal ("OAuth2" > "URL Generator").

Problem: The bot joins the voice channel but there's no sound.

• Solution 1: This is almost always an FFmpeg issue. Make sure FFmpeg is installed correctly AND that it's in your system's PATH. Open a new terminal and type ffmpeg -version. If you get an error, it's not installed correctly.
• Solution 2: Check your Discord client's output volume for the bot. Right-click the bot in the voice channel and make sure its volume isn't muted or set to 0.

Problem: Spotify, Deezer, or other platform links don't work or give errors.

• Solution: This usually means your API keys are missing or incorrect in your .env file. Double-check that you have correctly copied your SPOTIFY_CLIENT_ID and SPOTIFY_CLIENT_SECRET into the file. For lyrics, check your GENIUS_TOKEN. Remember to restart the bot after changing the .env file.

Problem: The bot says a video is "Age-Restricted" or "Unavailable".

• Solution: This is a limitation from YouTube. Some videos require a user to be signed in to view them, which a bot cannot do. Unfortunately, there is no fix for this. Please try finding another version of the song.

Problem: The music sounds laggy, stutters, or is delayed.

• Solution: This can be due to network issues between the bot's server and Discord's servers. Use the /reconnect command. This will refresh the voice connection and often fixes the issue without you losing your spot in the song.

Still Stuck? Get Help! (´• ω •`)

If your problem isn't listed here, please get in touch!

1. Join the Discord Server: Use /discord with the public bot or find the link on the main GitHub page. This is the fastest way to get help.
2. Open a GitHub Issue: If you're sure you've found a new bug, please open an issue. Provide as much detail as possible:
   • What command did you use?
   • What was the song/link?
   • What did you expect to happen?
   • What actually happened? (Include any error messages from the bot or the terminal!)