The package exhibits an inconsistency with the track.metadata object. This object appears to be tied to the song's position in the playback queue.
When playing a single song, track.metadata.bridge is populated correctly with bridge data, allowing the bot to provide accurate song information. However, adding a song mid-playback results in track.metadata.bridge becoming null for the song currently being added (any position other than 0 in the queue). This prevents the bot from replying with the correct information (like song's title and artist).
Attempting to force metadata retrieval using track.requestMetadata() proved ineffective. Even with Youtube sources explicitly blocked during player initialization, this method still returned Youtube metadata.
To Reproduce
Steps to reproduce the behavior:
Add song to queue.
Get metadata from the song via track.metadata.
Observe track.metadata.bridge being present.
Add another song to the queue while the first one is still playing.
Get metadata from the song via track.metadata.
Observe track.metadata.bridge being null.
Expected behavior
Ideally, track.metadata.bridge should consistently hold the correct bridge data irrespective of the song's position. Additionally, track.requestMetadata() should respect the main configuration and return data from the other accessible sources.
Screenshots
Not needed.
Please complete the following information:
Node Version: v21.4.0
Discord Player Version: v6.6.7
Discord.js Version: v14.14.1
Additional context
I'll list the returned jsons here. (but not fully since it's a lot of data and I don't want to make this comment longer than it is)
track.metadata when song is added on queue position 0.
Describe the bug
The package exhibits an inconsistency with the
track.metadata
object. This object appears to be tied to the song's position in the playback queue.When playing a single song,
track.metadata.bridge
is populated correctly with bridge data, allowing the bot to provide accurate song information. However, adding a song mid-playback results intrack.metadata.bridge
becoming null for the song currently being added (any position other than 0 in the queue). This prevents the bot from replying with the correct information (like song's title and artist).Attempting to force metadata retrieval using
track.requestMetadata()
proved ineffective. Even with Youtube sources explicitly blocked during player initialization, this method still returned Youtube metadata.To Reproduce Steps to reproduce the behavior:
track.metadata
.track.metadata.bridge
being present.track.metadata
.track.metadata.bridge
being null.Expected behavior
Ideally,
track.metadata.bridge
should consistently hold the correct bridge data irrespective of the song's position. Additionally,track.requestMetadata()
should respect the main configuration and return data from the other accessible sources.Screenshots
Not needed.
Please complete the following information:
Additional context
I'll list the returned jsons here. (but not fully since it's a lot of data and I don't want to make this comment longer than it is)
track.metadata
when song is added on queue position 0.track.metadata
when song is added on any other queue position.object returned on
track.requestMetadata()
even though youtube is blocked.