How to Fix “Player Moved Too Quickly” Warnings and Rubber-Banding

Direct answer

Do not disable security checks globally from one warning. Check whether the server is stalling at the same timestamp, whether the event follows a teleport/vehicle or movement plugin, and whether only one player/client is affected. Fix the lag or incompatible movement/anti-cheat behavior that produces the invalid movement.

What it means

“Moved too quickly” means the server rejected movement that exceeded what it considered valid for that update; lag, vehicles/teleports, movement plugins/mods, or cheating can all be involved.

If you are a player

Check whether the warning appeared while sprinting, flying, riding, being teleported or after a lag spike.
If it happens only with a specific mod or movement ability, provide that exact ability and client version.
Avoid repeatedly forcing movement through a protection system while the cause is unknown.

If you run the server

Correlate the warning with MSPT spikes and movement/teleport plugins at the same instant.
Reproduce in a safe location without speed effects, vehicles or custom movement; change one variable at a time.
Check for plugins applying velocity or teleport on the same tick; on Folia confirm region-safe scheduling.
Do not disable movement validation server-wide or blindly increase movement thresholds to hide an exploit or lag issue.

Verify the result: After the adjustment, repeat the exact movement path under normal player load and confirm no new rubberbanding or movement exploit appears.

References

Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.

Was this article helpful?

Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.