I think mobius might actually be onto something here. It won't complicate the code
at all to make this change (beyond a bit of backwards-compatibility stuff for replays and old format / other engine levels) either; it's pretty much just a matter of removing a "divide by 2" in one place in the physics code. The only downside is people would have to get used to the key values having changed (eg: RR 87, useful for some builder / platformer tricks, would now be RR 93), but I'd believe that if the Lix community was able to do this with SI, there's no reason the NeoLemmix community couldn't as well - and we'd still be keeping the system of 1 = slowest, 99 = fastest.
Likewise, most nice values will still come out nice. 99 is still 99. Any release rate that previously ended in 0, will now end in either 0 or 5 (eg: 90 is now 95; 80 is now 90; 70 is now 85; ... 10 is now 55). 1 is now 50, which is also a pretty nice value. The new "1" would be equivalent to what would be -97 under the current system, if negatives were allowed.
In fact, I'm even going to go ahead and say that, unless anyone comes up with a strong reason to object to it, I'm almost certianly going to use this idea.
For those of you who'd really rather have SI than RR, I'm also going to add an option to use SI instead.
In regards to maximum release rates being configurable per-level, it was discussed in the past and decided against (though this did lead to the introduction of the locked RR option; and one could argue that locked RR is just the most extreme case of setting a maximum). I'm not opposed to revisiting this if people's feelings have changed, though.
I didn't mean to offend anyone's levels. I was just making a broad statement. Obviously I think there will always be exceptions to any rule. I personally don't care for that level of precision in any level anymore but that's my own opinion.
Wasn't taking offence. Was genuinely interested in whether your thoughts (about requiring excessive precise RR manipulation being bad) still apply in cases like this, where precise is needed but excessive use of it isn't? Or maybe the reverse case, such as "Flow Control" from OhNo, which requires a lot of changes but they don't have to be particularly precise?