You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suppose may be a bug related to lavalink library, however I am using lavaqueue, so I think it's better place to report this bug:
When I reset discord bot without re-creating redis and lavalink containers and resume lavaqueue queue both queue.player.paused and queue.player.playing returns false, even if queue is paused/playing. This does not happen when using 'fresh' containers with redis and lavalink.
The text was updated successfully, but these errors were encountered:
This is an issue with the underlying library, so I'm moving this issue over there. I think it's a pretty easy fix if we set status to playing on the playerUpdate event.
I suppose may be a bug related to
lavalink
library, however I am using lavaqueue, so I think it's better place to report this bug:When I reset discord bot without re-creating redis and lavalink containers and resume lavaqueue queue both
queue.player.paused
andqueue.player.playing
returns false, even if queue is paused/playing. This does not happen when using 'fresh' containers with redis and lavalink.The text was updated successfully, but these errors were encountered: