24 Replies
client.moon.players.get('id').queue.all
rare-sapphireOP•2y ago
oh~
thanks
ðŸ«
You are welcome
rare-sapphireOP•2y ago
@1Lucas1.apk I'd like to search track and detect if it's already registered in queue, what should I do?
rare-sapphireOP•2y ago
Thanks you
Is there a workaround since there is still a queue or current when the player returns to destroy?
@1Lucas1.apk
Just add it to the options parameters
autoResume: true, resume: true
AutoResume is for when lavalink is inactive, and resume is when the client is inactive, then when it returns, moonlink recovers all data and continues
GG @릴리, you just advanced to level 1!
rare-sapphireOP•2y ago
I want all the data to be initialized when Player is destroyed
Could you explain better because I didn't understand correctly?
rare-sapphireOP•2y ago
If I Destroy Player, I want to Destroy the data in the current and queue together
@1Lucas1.apk
Destroy already does this
?play another love

<:Nota_Musica__Mlink:960665601574055966>╺╸
Title:
<:Estrela_Mlink:960660485999587348>╺╸
Uri:
<:emoji_21:967836966714503168>╺╸
Author:
7clouds Rock
<:emoji_23:967837516558393365>╺╸
Duration:
0 Days, 0 Hours, 4 Minutes, 3 Seconds

Request for: 1lucas1.apk
Tom Odell - Another Love (Lyrics) is playing now [ time test result: 862ms ]
?eval client.moon.players.get(message.guild.id)
?eval client.moon.players.get(message.guild.id).destroy()
?eval client.moon.players.get(message.guild.id)
rare-sapphireOP•2y ago
humm...
The Destroy method already deletes all data, from the database to player information
rare-sapphireOP•2y ago
If you create the player again after you destroy the player, the data remains the same
@1Lucas1.apk
No, they will be different, but some information may be the same such as guildId, voiceChannel, textChannel
Others may be different
And voiceChannel and textChannel can be different too
That in case a user enters another voice channel and has another chat, it will be different