[ BUG ] "reason":"STOPPED" instead of "reason":"FINISHED"

---

Describe the bug/issue.

My discord bot has TrackEnded function. This function is triggered by Victoria when a track ends. In this function i have a check like this:

if (!args.Reason.ShouldPlayNext())
          return;

With the latest version of Lavalink when the track ends and the reason is “STOPPED”. I downgraded to Lavalink 3.3.1.4 and the reason changed to “FINISHED” (as it should be). No errors shown in Lavalink.

Stacktrace / Screenshots

With Lavalink 3.3.2.1: [Victoria] {“op”:“event”,“reason”:“STOPPED”,“type”:“TrackEndEvent”,“track”:““,“guildId”:””}

With Lavalink 3.3.1.4: [Victoria] {“op”:“event”,“reason”:“FINISHED”,“type”:“TrackEndEvent”,“track”:““,“guildId”:””}

[Yucked]

I’m currently following the Lavalink issue dakata1337 opened and did ask him few questions. STOPPED was supposed to send only and only if you called StopAsync which meant to completely stop the player. But now, Lavalink is sending STOPPED for every normal track as well which is obviously going to make it extremely difficult to determine whether a user wants to stop the player all together or play the next song.

[dakata1337]

Please make sure v5.1.11 fixes your issue. v5.1.11 fixed all the issues i’ve had. Thank you for all the help @Yucked!