Closed GaoXanSheng closed 3 months ago
I suggest using an input box instead of a slider, as sliders can cause inaccurate numerical settings
Thanks for the report! In the latest beta, I’m now using the minimum and maximum values directly from the ranged attributes, if available.
Allowing free text input is on my roadmap, but it requires additional validation since the game tends to crash with unexpected values. For now, the sliders are a safer option to prevent this. Additionally, you can adjust the values using the arrow keys and mouse wheel.
I think we just need to determine whether the value is within the range of maximization and minimization If failed, set to default value Additionally, during testing, data rollers exceeding approximately 0.8E will not trigger
I noticed that the maximum upper limit value of the create Attribute Slider is hard coded, and this attribute should be obtained from existing attributes I used mixin to modify the property value, but the configuration did not change. Then I realized that this value was hard coded So can this feature be fixed? Or I can do it