Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When restarting the bot and leaving Lavalink running it wont reconnect to the old player #118

Open
JoniXTech opened this issue Dec 29, 2022 · 1 comment
Labels
enhancement New feature or request question Further information is requested

Comments

@JoniXTech
Copy link

When you try to leave Lavalink running (with a player running) and restart the bot, it won't reconnect to the player that is running rather create a new one. So the old player which is running cant be controlled anymore until it has a timeout.

Would it be possible to reconnect to the old player and control it again?

@0t4u 0t4u added the unverified Unverified bug that isn't replicated yet label Jan 19, 2023
@Deivu Deivu added enhancement New feature or request question Further information is requested and removed unverified Unverified bug that isn't replicated yet labels Jan 20, 2023
@Deivu
Copy link
Member

Deivu commented Jan 20, 2023

You need to create your own resuming system in this case, you need to "redo the players as they are" before you shutdown your bot, save it somewhere (database, file, or redis, your choice), then before shoukaku connects, you need to populate the players per node manually by creating it from the data you saved

@0t4u 0t4u mentioned this issue Feb 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants