Skip to content

maybe Bug #870

Closed Answered by Tomato6966
MrTabaOfficial asked this question in Q&A
Discussion options

You must be logged in to vote

Lavalink does not execute things via the websocket.

These are execution logs, from your client. means you told lavalink to execute "stop" (aka stop the track, if you have a queue system on the client, this is ment to skip in the queue and request the next song)
and then you executed "destroy" which tells lavalink to delete the player.

I assume, that you have on your client somehow said to skip the track, and then destroyed the player.

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by MrTabaOfficial
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants
Converted from issue

This discussion was converted from issue #869 on April 25, 2023 23:39.