You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add something like if (args.trim() === '') return; so that if the search request is empty, it won't send the request to LavaLink Server causing error 400, which unfortunately, but in When selecting a slashcommand, almost every time an empty request is invoked before pasting/searching for a song, which would help avoid unnecessary errors and spamming the LavaLink console.
Add automatic IP rotation to the bot, which would prevent several errors occurring when trying to play a song like Resource with requested id was not found","status":"404","code":"40400" I will add right away that this is not an error due to an incorrect existing link, but most likely due to the lack of IP rotation.
Due to the fact that the authors of LavaLink themselves warn about the deprecated use of YoutubeSourceManager - "[!WARNING] > The YoutubeSourceManager is now deprecated and won't receive further updates. Please use https://github.com/lavalink-devs/youtube-source#v2 instead."" I also suggest applying the changes mentioned in the warning.
If additional LavaLink nodes are defined in src/config.ts, automatic switching to them if the connection to the main node is lost etc..
Adding lyrics commands (including live lyrics synchronized on the fly text to music [e.g.: using LavaLyrics from Topi] and a general lyrics command that will send the lyrics of the entire song.
After adding another song, the play/stop button sometimes doesn't update (photo 1), and sometimes it crashes that it is loading, that the song has been added to the queue and doesn't display the embed (photo 2), as if it has a temporary suspension, and this 1 error fixes itself after removing the bot from the channel and asking the question again (but after some time it randomly comes back too), and this 2 thing is just a random moment, so it's even hard to determine more accurate information.
The text was updated successfully, but these errors were encountered:
Hello, Here they are
Add something like
if (args.trim() === '') return;
so that if the search request is empty, it won't send the request to LavaLink Server causing error 400, which unfortunately, but in When selecting a slashcommand, almost every time an empty request is invoked before pasting/searching for a song, which would help avoid unnecessary errors and spamming the LavaLink console.Add automatic IP rotation to the bot, which would prevent several errors occurring when trying to play a song like
Resource with requested id was not found","status":"404","code":"40400"
I will add right away that this is not an error due to an incorrect existing link, but most likely due to the lack of IP rotation.Due to the fact that the authors of LavaLink themselves warn about the deprecated use of YoutubeSourceManager - "[!WARNING] > The
YoutubeSourceManager
is now deprecated and won't receive further updates. Please usehttps://github.com/lavalink-devs/youtube-source#v2
instead."" I also suggest applying the changes mentioned in the warning.If additional LavaLink nodes are defined in src/config.ts, automatic switching to them if the connection to the main node is lost etc..
Adding lyrics commands (including live lyrics synchronized on the fly text to music [e.g.: using LavaLyrics from Topi] and a general lyrics command that will send the lyrics of the entire song.
After adding another song, the play/stop button sometimes doesn't update (photo 1), and sometimes it crashes that it is loading, that the song has been added to the queue and doesn't display the embed (photo 2), as if it has a temporary suspension, and this 1 error fixes itself after removing the bot from the channel and asking the question again (but after some time it randomly comes back too), and this 2 thing is just a random moment, so it's even hard to determine more accurate information.
The text was updated successfully, but these errors were encountered: