Open 5HT2 opened 3 years ago
Suggestions:
Ability to input negative ammounts. Useful for things like ItemModel.
This isn't a GUI thing as much as it is a setting thing. None of the settings allow negative values, though they could.
I think a power user solution would be to allow the user to set any value with the ;set command, ignoring the gui limits. If someone is using commands and they mess up, it's their fault.
Future does the same thing as well. I think it's the easiest way to idiot proof the GUI while allowing power users to set whatever they want
Ability to input negative ammounts. Useful for things like ItemModel.
This isn't a GUI thing as much as it is a setting thing. None of the settings allow negative values, though they could.
I think a power user solution would be to allow the user to set any value with the ;set command, ignoring the gui limits. If someone is using commands and they mess up, it's their fault.
Future does the same thing as well. I think it's the easiest way to idiot proof the GUI while allowing power users to set whatever they want
No. It always allow negative number if the range allows. And no, it would causes weird bugs to make it ignores limit and handling it in code side would create tons of bloat plate code.
And no, it would causes weird bugs to make it ignores limit and handling it in code side would create tons of bloat plate code.
That's fine imo. If the user uses a set command or something to set a value out of range that's their fault.
And no, it would causes weird bugs to make it ignores limit and handling it in code side would create tons of bloat plate code.
That's fine imo. If the user uses a set command or something to set a value out of range that's their fault.
It isn't. If it causes crash then resetting the value will be pain. You have to go into the config and search then edit it manually. 🗿
Okay I guess
For after #1510 is merged.