Allow customizing subterranean movement speed and allow parsing floating point Speed values #1406
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should fix an issue introduced in 890eca0 for tunnel locomotor where a distance check was made against unit's current speed without ensuring that
SpeedPercentage
which is normally not used byTunnelLocomotionClass
is 1.0 instead of 0.0 and unhardcoding the subterranean movement speed.Subterranean unit travel speed
Speed
multiplied by[General]
->TunnelSpeed
.In
rulesmd.ini
:Unit
Speed
setting now accepts floating-point values. Internally parsed values are clamped down to maximum of 100, multiplied by 256 and divided by 100, the result (which at this point is converted to an integer) then clamped down to maximum of 255 giving effective internal speed value range of 0 to 255, e.g leptons traveled per game frame.