Sanitize player position and speed server-side #12396
Merged
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.
fixes #11742 (effectively in the case we care about)
As the source code comment suggests enforcing the f1000 bounds doesn't actually make much sense, but this PR fixes the issue and can be safely merged into stable branches without fearing regressions.
In the future (for 5.6, after this PR)
CHECK_FLOAT_RANGE
should be removed entirely and the restriction only enforced (viaclampToF1000
) in the places where it's still relevant:To do
This PR is Ready for Review.
How to test
*
**
*** You can easily tell whether the position shifting worked by seeing if entities near you disappear while you hold the key combo.