#How to prevent Lavalink from disconnecting when restarting a bot
1 messages · Page 1 of 1 (latest)
When you restart your JavaScript application, save the current playing players (current queue, current track, position) into a database table. When the app loads (or shards), restore these players and then delete them from the database
I understand, it's not supported separately by modules like lavacord, right?
You should also store guild id/voice channel id
Oh, I don't know. But I don't think so; most clients handle when the Lavalink node goes down, not when the client goes down