Lavaclient event handlers listening to deprecated event names #1123
Assignees
Labels
branch:next
Issues: Impacts next branch
branch:stable
Issues: Impacts stable branch
priority:p3
Issues and PRs: Low priority
released on @next
released
status:confirmed
Issues and PRs: Confirmed bug, or enhancement is confirmed to be added
type:bug
Issues and PRs: Related to a bug
Comments
github-actions
bot
added
priority:p3
xayanide
added
branch:stable
xayanide
changed the title
15 tasks
15 tasks
|
🎉 This issue has been resolved in version 7.0.2-next.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This issue has been resolved in version 7.0.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
As of Lavaclient v5.0.0, there were changes to event names.
lavaclient/lavaclient#87
This was probably overlooked in 57fb40d
This results in a bug where Quaver's lavaclient event handlers for connect and disconnect to not work.
connectshould now beconnecteddisconnectshould now bedisconnectedQuaver/src/events/music/connect.ts
Line 11 in aec3415
Quaver/src/events/music/disconnect.ts
Line 4 in aec3415
File names should follow the change respectively.
I learned about some new events in Lavaclient that might come in handy later:
The
readyeventThe
queueCreateevent.Severity
Low
Affected branches
Quaver version
7.0.1
Steps to reproduce
Expected behavior
Show an indication that Lavalink has either connected or disconnected.
Actual behavior
No indication.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: