-
Notifications
You must be signed in to change notification settings - Fork 208
Bot doesn't leave when left alone #605
Comments
Sorry for the late reply. Some users prefer having the bot remain connected. The large public FredBoat closes any unused voice connections for performance reasons. I would be more concerned about the fact that your bot is left in a broken state. Is it a concern of yours that the bot remains in the channel? |
No worries! The workaround is to simply Yeah, you're right. The main issue is that it ends up in this state. I think this can happen even though people don't leave the channel. If you simply leave the bot in a non-playing state for too long, it will just stop working. Is there any specific logs you want to take a look at when this happens? |
I don't think logs will help, but I should be able to reproduce this locally. |
This issue is still there as far as I tested. At first I thought it's my problem, but it seems that it's not after I crontab to auto-update fredboat
I think I've encountered the same issue as @anton-johansson Thank you! |
I've just hosted FredBoat myself using Kubernetes, which works great. However, if the bot is left alone, it doesn't leave the channel. It just stops playing and prints this:
Whenever I want to come back and play something, it's stuck in some weird state. I have to force it to leave with
!leave
before I can play anything. So it would be great if I could have the bot leave automatically when left alone instead, as this would solve my issue.Is there any way to force it to leave when left alone?
The text was updated successfully, but these errors were encountered: