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
Describe the bug
When actively playing a video, increasing the volume via reaction button when already at 100% causes a This interaction failed error to appear between the reaction buttons. This affects the latest repository version of the bot.
How To Reproduce
Steps to reproduce the behavior:
Play a song.
While the volume is at 100%, press the volume up reaction button.
Error appears.
Expected behavior
An error message should not appear. A message stating that the volume is already at 100% would likely be a better notification sent via user-only interaction message.
Environment (add if possible)
Node.js version: 22.2.0
NPM version: 10.8.0
Additional information & screenshots
I have not tested this with the volume down button when already at 0%, but this likely already exists. I am also not sure if starting with lower default volumes and increasing/decreasing to these levels would trigger it or not. (I'd assume so). My default volume via my config.json is already at 100%.
The text was updated successfully, but these errors were encountered:
krakenftw
added a commit
to krakenftw/evobot
that referenced
this issue
May 31, 2024
Added checks while changing volume, on 100 volume the volume up button is disabled and same for
volume 0. Improves UX and removes the interaction failed as showed in eritislami#1628fixeritislami#1628
Describe the bug
When actively playing a video, increasing the volume via reaction button when already at 100% causes a
This interaction failed
error to appear between the reaction buttons. This affects the latest repository version of the bot.How To Reproduce
Steps to reproduce the behavior:
Expected behavior
An error message should not appear. A message stating that the volume is already at 100% would likely be a better notification sent via user-only interaction message.
Environment (add if possible)
Additional information & screenshots
I have not tested this with the volume down button when already at 0%, but this likely already exists. I am also not sure if starting with lower default volumes and increasing/decreasing to these levels would trigger it or not. (I'd assume so). My default volume via my
config.json
is already at 100%.The text was updated successfully, but these errors were encountered: