Request: Fix range of speed gauge so that 0 = 0, 15 = 256, and other steps are strictly logarithmic.
nycki93 opened this issue ยท 4 comments
When a vanilla comparator reads an empty chest, it reads 0, ticking up to 1 for the first "nonempty" level, and ticking up to 15 when the chest is completely full. The speed gauge should have the same "min" and "max" ability, instead of ticking up to 15 when the speed reaches 205 (the max is 256).
Additionally, since speed is most often manipulated by doubling or halving it, the scale should be logarithmic. The current system is to use a piecewise function that picks "slow", "medium", or "fast", and then divides each range up linearly.
| comparator reading | current motor threshold | desired motor threshold |
|---|---|---|
| 0 | 0 | 0 |
| 1 | 1 | 1 |
| 2 | 5 | 2 |
| 3 | 10 | 3 |
| 4 | 15 | 4 |
| 5 | 20 | 6 |
| 6 | 24 | 9 |
| 7 | 29 | 13 |
| 8 | 42 | 19 |
| 9 | 59 | 28 |
| 10 | 76 | 40 |
| 11 | 92 | 58 |
| 12 | 115 | 84 |
| 13 | 145 | 122 |
| 14 | 175 | 177 |
| 15 | 205 | 256 |
This issue has been marked as stale because it has been inactive for 3 weeks. It will be closed if it remains inactive for another 3 weeks.
This issue has been marked as stale because it has been inactive for 3 weeks. It will be closed if it remains inactive for another 3 weeks.