TransWikia.com

WARNING playername moved too quickly!

Arqade Asked on April 20, 2021

I am running a dedicated vanilla 1.6.1 server so that my friend over in America can connect and play along with me. The server is whitelisted, we’re both in the list and have OP permissions. Playing creative mode.

We’re building TNT cannons, some of which are designed to launch your player. We built one example which can launch a player over 700 blocks high – and my friend has no problem using this.

However, when I step in and launch myself, as the server host, it tells me that I am moving too quickly. My position is reset and I don’t get launched in to the air. I have tried setting the allow-flight flag in the server properties file to true, but it still causes the warning to show.

Any ideas as to why I am affected, but my friend isn’t?

Computer specs:

  • Intel i5 3570k processor @ 4Ghz
  • 8GB DDR3 @ 1500 Mhz
  • Sandisk Pulse SSD
  • NVIDIA GTX 670

Minecraft runs in windowed mode, but maximised.

My ping to the server is < 1ms (obviously), friend’s ping is about 140ms.. Give or take 10ms.

3 Answers

My bukkit server still has the kick-on-speedhack parameter in the bukkit.yml file, but that might not be evidence of it being deprecated.

Add: kick-on-speedhack: false

under settings: anyway to give it a go if you haven't already.

Answered by benstapleton on April 20, 2021

I had a similar issue on an Agrarian Skies server.

All players within the affected area/chunk were getting stuck in place (I don't like getting reset back to the same spot repeatedly) and the server window was spammed with the moving too fast message.

We did find a suggestion to allow flight was helpful in clearing us from being stuck sooner however it did not resolve the issue.

Because it was within a 'bee' production area we pinpointed that the bees were causing the issue. We eventually resolved this by using an Inoculator (from Extra Bees mod) to remove the GRAVITY affect from certain bee types. Without the affect there is was no further spam to the server and we didn't get stuck in the environment around the bee production area. Just watch the bee doesn't revert to having the affect again (this happened a few times to me).

Answered by Jevanna on April 20, 2021

For others who may come here, I was able to fix this on my vanilla server by setting

allow-flight=true

in the file server.properties.

Answered by deltaray on April 20, 2021

Add your own answers!

Ask a Question

Get help from others!

© 2024 TransWikia.com. All rights reserved. Sites we Love: PCI Database, UKBizDB, Menu Kuliner, Sharing RPP