We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable creative mode and fly quickly.
The server will display warnings like this:
Additionally, the server-authoritative-movement setting in server.properties is not functioning as intended.
server-authoritative-movement
server.properties
Even changing from server-auth to client-auth does not disable the rollback.
server-auth
client-auth
The text was updated successfully, but these errors were encountered:
set player.setCheckMovement(false); and cancel PlayerInvalidMoveEvent
Sorry, something went wrong.
在 PlayerInvalidMoveEvent 之前有一个 if (invalidMotion) 判断
if (invalidMotion)
可以看下面这段从 Player.java 摘录的片段。
protected void handleMovement(Vector3 clientPos) { if (!this.isAlive() || !this.spawned || this.teleportPosition != null || this.isSleeping()) { return; } boolean invalidMotion = false; Location revertPos = this.getLocation().clone(); double distance = clientPos.distanceSquared(this); if (!this.level.isChunkGenerated(clientPos.getChunkX(), clientPos.getChunkZ())) { invalidMotion = true; this.nextChunkOrderRun = 0; } else if (distance > 128) { invalidMotion = true; getServer().getLogger().warning(String.format("%s moved too far (%.2f)", this.getName(), distance)); } if (invalidMotion) { this.revertClientMotion(revertPos); return; } // more code...
No branches or pull requests
🐞 Bug Feedback | BUG反馈
📝 Bug Description | BUG描述
Enable creative mode and fly quickly.
The server will display warnings like this:
Additionally, the
server-authoritative-movement
setting inserver.properties
is not functioning as intended.Even changing from
server-auth
toclient-auth
does not disable the rollback.📸 Screenshots / Video
45733f6-32c-a414-ee74-eeaf87f102a3.mp4
The text was updated successfully, but these errors were encountered: