Players Rubber-Band After Teleporting

Direct answer

Measure server tick health and identify movement/anti-cheat plugins before blaming the player connection.

Rubber-banding means the client and server disagree about accepted movement, often during lag or movement checks.

Note whether the teleport is from a command, portal, plugin menu or cross-server transfer.
Record whether you land back at the origin, fall through unloaded terrain or briefly see the destination before returning.
Reproduce once from a quiet area and provide the timing rather than repeatedly spamming teleport commands.

Correlate the teleport with server MSPT, chunk-load time and any subsequent teleport or anti-cheat event.
For network transfers, verify Velocity/Bungee route and whether the destination backend is ready and player data is loaded.
Review world-border/region protection and plugin cancellation messages. On Folia, use the platform’s supported asynchronous teleport scheduling instead of cross-region synchronous access.
Test a single known destination after preloading its chunk; do not solve this by disabling all movement checks.

Verify the result: Player position should remain at the intended destination after relogging, without movement violations or data rollback.

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.