-
Notifications
You must be signed in to change notification settings - Fork 23
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
[Question] How node player resume works #40
Comments
you need to call node.updateSession(true) in order to activate resuming. aka |
https://github.com/Tomato6966/lavalink-client?tab=readme-ov-file#version-200 # Node Resuming got supported
# First enable it by doing: (It's now called updateSession)
+ await player.node.updateSession(true, 360_000);
# then when reconnecting to the node add to the node.createeOptions the sessionId: "" of the previous session
# and after connecting the nodeManager.on("resumed", (node, payload, players) => {}) will be executed, where you can sync the players!
# Node Options got adjusted # It's a property not a method should be treated readonly
+ node.resuming: { enabled: boolean, timeout: number | null };
|
I see, thank you so much! |
What I mean is, when a node goes offline, all players go offline.
Then, the manager tries to reconnect to the node and the player plays again.
With shoukaku this is automatically, but in the case of
lavalink-client
, what would it be like? Because if you put thesessionId
in the nodes array, in My case it didn't seem to work.The text was updated successfully, but these errors were encountered: