Requester return `null`
54 Replies
fascinating-indigoOP•15mo ago
@1Lucas1.apk
Hello
fascinating-indigoOP•15mo ago
hi, i'm trying to get the requester of the track but it returns null
To set the requester before adding the track you have to do the following
track.setRequester(user)
fascinating-indigoOP•15mo ago
yeah i tried that but still return
null on trackStart event
GG @Louis, you just advanced to level 1!
fascinating-indigoOP•15mo ago
tried to do
track.requester = user but the requester field still returns nullAre you testing using playlist?
fascinating-indigoOP•15mo ago
yeah
Too bad I can't test it now 😦
I'm redoing the entire package
Have you tried putting console.log(track) to see if the property is assigned?
fascinating-indigoOP•15mo ago
yeah, the result is the same with the first image on the top
for (const track of result.tracks) {
track.setRequester(interaction.user)
console.log(track)
fascinating-indigoOP•15mo ago
this returns the user, but in the event it doesnt
Which version are you using?
fascinating-indigoOP•15mo ago
2.16.60
fascinating-indigoOP•15mo ago
also sometime the player playing the random song that's not added to the queue (loadType is search)
This removes the autoPlay parameter, or set false
fascinating-indigoOP•15mo ago
removed it before
fascinating-indigoOP•15mo ago
It does not have?
fascinating-indigoOP•15mo ago
yeah
may it's playing the old queue from the db?
Put the parameter and set it to false
It deletes the jsons when restarting
Try putting a log in
console.log(player.current)fascinating-indigoOP•15mo ago
same with track
fascinating-indigoOP•15mo ago
Yes
fascinating-indigoOP•15mo ago
the bot still in the vc after restart
There is a parameter in moonlink, to continue playing and resume the connection with lavalink and continue the process
fascinating-indigoOP•15mo ago
oh jeez
In MoonlinkManager there is the
resume parameterGG @Louis, you just advanced to level 2!
You remove it to deactivate
fascinating-indigoOP•15mo ago
is it
true by default?No
What version of nodejs are you using?
fascinating-indigoOP•15mo ago
fascinating-indigoOP•15mo ago
latest lts
20.10.0
The problem with setting the track, I will fix it using the lavalink parameter
fascinating-indigoOP•15mo ago
v2 seems to have a lot of bugs
jeez
That's why I'm doing it ðŸ¤
fascinating-indigoOP•15mo ago
nvm i still love how this package works
just some buggy
I don't know if it's from NodeJs but in v18 it works fine
For me it works well in this version, I don't know in others
fascinating-indigoOP•15mo ago
don't think so, i'm currently building a lavalink package too but still need more time to finish it
if nodejs version, it's only happend when they are using the lower version
not higher
But there may be other factors
fascinating-indigoOP•15mo ago
yeah, i think you should not edit the response data with custom structure, just keep it like how lavalink docs said
still better if the lib docs are not complete 100%
I leave it like this to keep the package working as best as possible.
Instead of the package working with different data, treating everything in the same way
Save lines
fascinating-indigoOP•15mo ago
just make it simply and based on 100% rest api
easier when debugging and upgrade the code
yeah, just complete the lavalink thing first, then add the features
I didn't understand anything you were saying
fascinating-indigoOP•15mo ago
.-.
I mean you should make it 100% api based first, don't try to change the structure or anything. Once you've done that, then continue adding features to your library
I plan to keep it that way 🙂
fascinating-indigoOP•15mo ago
Goodluck then
It's not the problem with the package, it's working correctly
Look man, I'm not going to change the shape of the package because just one user didn't like the way it handles the data
I like it this way, it helps other users to deploy their music bot more conveniently
Instead of complexity
fascinating-indigoOP•15mo ago
can i see the console.log part of the trackStart?
GG @Louis, you just advanced to level 3!
Yes