Teleport causes a large amount of `moved too quickly!` logs
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 12.7k
- Forks
- 3.5k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 11
Description
Expected behavior
No log caused by teleport.
Observed/Actual behavior
Far more than below are printed sometimes. (But no log is printed at other times. It's random)
[19:55:46 WARN]: NoyException moved too quickly! -221.0,1.0,-482.0
[19:55:46 WARN]: NoyException moved too quickly! -221.0,1.0,-482.0
[19:55:46 WARN]: NoyException moved too quickly! -221.0,1.0,-482.0
[19:55:46 WARN]: NoyException moved too quickly! -221.0,1.0,-482.0
[19:55:46 WARN]: NoyException moved too quickly! -221.0,1.0,-482.0
[19:55:46 WARN]: NoyException moved too quickly! -221.0,1.0,-482.0
Steps/models to reproduce
public boolean teleport(Player player, Location location) {
var success = false;
if (player.getWorld() == location.getWorld()) {
success = player.teleport(
location, TeleportFlag.EntityState.RETAIN_VEHICLE, TeleportFlag.EntityState.RETAIN_PASSENGERS); // LOGS ARE PRODUCED HERE
} else {
player.eject();
success = player.teleport(location);
}
return success;
}
Just need to call it once.
Plugin and Datapack List
No other plugins or datapacks
Paper version
This server is running Paper version 1.21.10-84-main@bac3da1 (2025-10-20T02:11:40Z) (Implementing API version 1.21.10-R0.1-SNAPSHOT)
You are running the latest version
Previous version: 1.21.10-81-7845cba (MC: 1.21.10)
Other
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the Java teleport(Player, Location) method and the RETAIN_VEHICLE/RETAIN_PASSENGERS flags on Paper 1.21.10-84. Trace where the “moved too quickly!” warning is emitted after teleport; done means the shown teleport no longer produces spurious warnings while preserving teleport behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100