During my testing, my client was looking for a resumed field but was not seeing it, and throwing an error causing the websocket connection to be immediately terminated with no attempt at reconnecting. I don't believe this is the duty of clients to change as this server markets itself as being generally compatible with clients, thus the core implementation should at least match that.
Checkmarks
[x] The modified endpoints have been tested.
[x] Used the same indentation as the rest of the project.
Changes
This changes the
resume
field toresumed
to be inline with what Lavalink clients should expect, as per the implementation documentation at https://lavalink.dev/api/websocket.html#ready-opWhy
During my testing, my client was looking for a
resumed
field but was not seeing it, and throwing an error causing the websocket connection to be immediately terminated with no attempt at reconnecting. I don't believe this is the duty of clients to change as this server markets itself as being generally compatible with clients, thus the core implementation should at least match that.Checkmarks
Additional information
N/A.