Feature Description
I find even 20% is actually quite loud and I dont imagine the top 50% of the bot's volume is particularly useful for the vast majority of users. With this in mind I think it would make the user experience better to allow for a configurable default volume (it can currently be overridden but only by editing the code so any changes are gone when you update), and a maximum volume so you can provide the expected loudest volume.
Use Case
example config
maximum volume: 50
Default volume: 50
From this configuration when the bot starts it would set the ceiling of the volume value to be 50% of the total possible volume, and the 50% value would be 100% in the UI.
The end result of these config values would mean that the user would see "50%" as the starting volume. And each click of the button would still go up or down 10% of the selected maximum value (I believe this would require that the step value be calculated on initialize to be 10% of the maximum instead of just a 0.1f value) until it reached 0 or the set ceiling.
Category
Configuration
Could this be an extension?
No — this needs core changes
Alternatives Considered
No response
Additional Context
No response
Feature Description
I find even 20% is actually quite loud and I dont imagine the top 50% of the bot's volume is particularly useful for the vast majority of users. With this in mind I think it would make the user experience better to allow for a configurable default volume (it can currently be overridden but only by editing the code so any changes are gone when you update), and a maximum volume so you can provide the expected loudest volume.
Use Case
example config
maximum volume: 50
Default volume: 50
From this configuration when the bot starts it would set the ceiling of the volume value to be 50% of the total possible volume, and the 50% value would be 100% in the UI.
The end result of these config values would mean that the user would see "50%" as the starting volume. And each click of the button would still go up or down 10% of the selected maximum value (I believe this would require that the step value be calculated on initialize to be 10% of the maximum instead of just a 0.1f value) until it reached 0 or the set ceiling.
Category
Configuration
Could this be an extension?
No — this needs core changes
Alternatives Considered
No response
Additional Context
No response