When players are jumping from a high place (around 50 blocks or higher) They get teleported back and the server states "Player/Vehicle moved too quickly!".
To reproduce:
Jump from a high place using an Elytra (In gamemode Survival or Adventure),
Look down to gain momentum,
Just before you fall to your death, look forward to move very fast, the server will see this as possible cheating and output the warning that players might be cheating.
OR:
Go to spectator mode
/gamemode spectator
Scrollwheel Up a few times to set the speed to maximum
Fly for a bit and look at the server stdout
Related issues
is duplicated by
relates to
Attachments
Comments


Here's what it looks like: http://i.imgur.com/C5Viayn.gifv
Breaking for cool maps 😞

This is happend to me also, in creative mode (and survival), when i'm gliding fast with Elytra

I can support this as well. Once I was flying over a the nether lava sea and this glitch ended up nearly killing me.

Can confirm, also happens when in spectator mode and flying fast.

spectator and flying to fast is included in MC-90061

Still happening for me in 15w45a with Elytra and spectator mode.

people, spectator mode is MC-90061

Can anyone confirm this issue without specator mode ?

in 15w45a, yes, people were just saying "confirmed for elytra and confirmed for spectator"

Correct, it happens in both survival mode and creative mode using Elytra. The spectator mode issue was in addition to that, it just has the same behavior.

After some reading on the wiki it seems that the highest velocity a player should be able to reach by falling is around 70m/s. From what I can tell from testing the server will stop you if you get to around 10m/s so that's probably the cause of this bug. So it's nothing to do with the Elytra or spectator like in the other bug, just a cap on vertical movement speed.

Still occurring in Snapshot 16w02a

still occuring

@unknown the max spectator flight speed is MC-90061, please remove that part from the title and description again; next time please search before changing the report

FVbico why not put them all into 1 report? They're all caused by a limit on player speed.

true, but they're already marked as related and have been kept apart for about 3 months now
and still, the spectator issue was reported earlier (1 ticket before this one) so @unknown actually made that part duplicate of MC-90061

Fair enough, as long as they're all marked as related it should be easy for the devs to see.

Happen to speed effect.

@Huang Hai Gamer!: what amplifier did you use?

Still occurs in 16w03a, especially in survival mode with boats, it practically shuts off the server.
http://imgur.com/6t2Bwui
Confirmed for 16w04a

I think this bug needs writing that it not only spams the log, but also rubber bands the player like this: http://i.imgur.com/C5Viayn.gifv
Currently what's written about the bug doesn't hint towards this at all, making it look like just a 'console text spam' bug.

They know it also happens as that message is the result of the rubberbanding which is caused by the improved anti-cheating mechanic

Confirmed for 16w05b

As of 16w07a there is a new gamerule called disableElytraMovementCheck
, defaulting to false. Does setting this to true fix the elytra part of this issue for anybody?
/gamerule disableElytraMovementCheck true

Yes, that gamerule fixes this issue!

Just a quick question as this bugpost got closed: Does that also fix the boat issue, or only the Elytra issue?
Any SMP owners who can tell that? @unknown ?

I can say that the spectator mode part is still a issue if the gamerule is false, not for true.
but I don't think this effect should be controlled by a gamerule that defaults to false, as it happens even when not cheating, what is it supposed to do anyway?

Well it's a bit of a hacky fix to be honest. What it does is allows players flying an elytra through the server's built-in anti-cheat, meaning it doesn't spam them from moving too quickly and doesn't lag them out either. Haven't been able to test with boats; do they even travel that fast anymore?

Still a problen with boats in 1.9-pre1 (MC-97468) please reopen

Although happy about the fix, I was expecting some kind of server property that goes along the lines of a maximum momentum at which the anti-cheat kicks in.
Seems like it would fix all parts of the bug, and fit with it only affecting servers.

Are boats still an issue in pre-2, can someone please confirm this? @unknown ?

Please reopen, this is in no way fixed at all.
Still completely broken.

@unknown Could you (and anyone) explain it more detailed?
Only affects boats? Ways to reproduce?

as well as spectator, full speed+sprint on my server, going into unloaded chunks before they are loaded makes me be put back (although my server does have other issues (runs 10 TPS instead of 20)
[21:46:35] [Server thread/WARN]: FVbico moved too quickly! 18.87734290432641,0.0
,-16.83755755225667

@unknown: Unicorn speed / Unicorn server stdout ?

STDOUT = standard output - so probably "look at Unicorn server stdout" means probably it's their steady server/console output
Unicorn made me chuckle >.>
Maybe their server name, either so that it can be confirmed there, or as ad? 😸

sorry, but my server isn't open to public, and I'm working on a project for 2 years in the axcact same world now

@unknown: Thx for the attempt of explanation, I know well 1> but what's your explanation of set Unicorn speed to maximum in this context ?

@unknown When you're in spectator mode you can get faster when you use your scrollwheel - so they probably mean the maximum available/allowed speed there is possible in GM3 on their server? Maybe they're not native English speakers and just phrased it a tad strangely? Maybe they can fly unicorns on their server ;-;?
Sorry for any meta-blabbering, but I need to hold back to not spill my water over my screen, don't expect me to make any serious assumptions, I'm on the edge of my composure

Sorry, I got pranked and the description got messed up.

M/C ver : 1.9 full release, currently allocated 20gb ram (increase from 8gb seems to have helped)
O/S : tried on CentOs 7 and Ubuntu 14.04 LTS
Java : tried with openJDK 7 & 8 and oracle 7, 8 & 9(dev)
Box Spec :
xeon 1225 v3 QC @ 3.6 Gig
256 Gig Ssd raid
Gig Network
Managed by : tried Mcma, MineOs & cli launch
Same errors as listed above - essentially anything that's able to act as a 'vehicle' for the player capable of moving fast : elytra, boats, horses (including skeleton) and donkeys - minecarts don't appear to cause an issue. In some cases our logs are showing horses with no passenger also causing the error.
Errors can be generated at any time - no obvious other activity / trigger event happening at the same time.
Typically the errors become significantly worse and more frequent as number of users increases. Have determined currently that maximum users seems to be around 30 before causing the server instance to crash/terminate.

Confirmed

I can not run, use the minecart, boats and wings! Minecraft 1.9 - 1.9.1 pre 3 (vanilla) I had no such problems 1.8

This behaviour is also caused by self-moving piston contraptions when ridden by a player.

Minecraft 1.9.3 Pre-Release 1 - the problem persists. Reopen!

It wasn't closed.

1.9.3 Pre-Release 1 has this, does not appear to have been fixed for Pre-Release 2

Ideas for fixes:
Factor gamemode into fastest possible velocity calculations.
Factor swiftness effect into fastest possible velocity calculations.
Add a gamerule such as
check-player-velocity
(default true) to allow servers to turn this "feature" off; Spigot already does this.

Affects velocity when landing and rebounding off slime blocks as well. Also disrupts upward velocity from TNT human cannon.

The error is not corrected in 1.9.4! Test minecraft_server.1.9.4.jar on OS Windows 10, Windows Server 2016 Pre 5, Linux Mint, Ubuntu, Knoppix. PC 4 Core 8 threads, 16Gb Ram 2400mhz, Corsair Neutron GTX SSD. connected by GbLAN Ping 1ms. In the fall to 50+ blocks, flight on elytra, a boat on the ice, use minecart - Server spam "Player moving too quickly"

I get this servermsg by simply going through portal.


I almost never ran into this until 1.9.4, and I used spectator mode at high speeds a lot. But now I run into it a lot, particularly with Elytra.
(my own duplicate of this report: MC-102971, just for the record)
For those just coming across this bug due to its effects on Elytra, the following server command solves the problem for me:
/gamerule disableElytraMovementCheck true
Thank you Skylinerw for finding and pointing this out.

Confirmed in 1.9.4 when falling very far, caused me to be tped back up and fall again.

Also note that this physically moves you back; could OP please update the description?
Edit: thanks

Confirmed for 1.10, this also applies to really powerful TNT cannons which is such a shame. There should at least be a way to disable this anti cheat thing in the server.properties file.

Confirmed for 1.10.2, also happens while sprint-flying in creative and sometimes by the piston translocation bug (which teleports the player back and forth up to six times (writing in the console the player is moving too fast every teleport)).
Before I changed the gamerule disableElytraMovementCheck to true, I gave me a punch 15 bow and whenever I shot myself with it, (after the moved too fast message) from the client perspective I stopped and teleported 10-15 blocks down, but for the server (and any other players), I didn't. So any arrow I shot appeared up there and a little in-front (to the direction I was flying when teleported), mobs tracked me to there, and after I landed (from the view of the client) I was still in flight mode 15 sec. or so, waiting for the actual me to land. After he did, even If I was looking straight down, I didn't took any damage from the landing, and any other players could see me landing and immediately teleport to the client location (I even saw a creeper who tracked me flying and after the server me landed, just stopped and started wondering about (like creepers that don't see a player in survival/adventure do)).

It also happens when you're flying at maximum speed in spectator mode.

I think this also causes the effects of MC-86850.

confirmed for sprint flying in creative and high spectator speeds for 16w40a. especially prevelent with higher ping

I was running into this issue on a modded 1.10 server (with a flight item in survival mode).
To 'fix' it, I quadrupled the amount of memory allocated to the server in the .bat file I used to launch it.
Now I only run into this issue if I'm flying at full speed into newly generating chunks.
I suspect that vanilla servers will behave in a similar way, and that this actually is intended behavior, and not a bug.

Can confirm. It happens to me when I run the server and the game on the same computer : seems to be a resource problem.

Comfirmed in 16w44a

Comfirmed in 1.11 - in Gamemode 1 and with op i get mass "moving too quickly" messages

Confirmed in 1.11.2

Confirm having same issue with a vanilla server. Current setups:
Running 1.11.2 server on:
Core i5-3570 3.4ghz
24GB DDR3 12800
Silicon Power S60 120GB SSD
Windows Server 2012 r2 Datacenter
Java Version 8 Update 111
Startup command: "C:\Program Files\Java\jre1.8.0_111\bin\java" -Xmx4G -Xms2G -jar c:\minecraft\MinecraftServer2\server.jar nogui"
Running client on:
Core i5-3570 3.4ghz
16GB DDR3 12800
Kingston SSDNow V300 120GB
AMD Radeon R7 250 2GB (PCI-E 3.0 x8)
Windows 10
Java Version 8 Update 111
Using JVM Argument -Xmx4G
Happens when flying quickly or falling large distances.

Having this issue in 1.11.2, happens when flying quickly, especially when flying in spectator and then sprinting.
Isn't this basically caused by anti-cheat measures? and if so shouldn't this be configurable in the server properties at the very least or be adjusted to account for maximum speeds on minecart, elytra, horse, creative and spectator?

already marked as affected.
There's already a gamerule to turn it off, but it is a valid bug as it's too strict as of now (no lag(client and server) still triggers it) else this would've been closed already.

Gamerule does not fix this for spectator, as expected.

Sadly still in 1.12

Which gamerule allows you to turn this off? and does that then prevent you from losing all speed when travelling at max speed with elytra?

@unknown gamerule disableElytraMovementCheck true
As far as I know, that gamerule just lets servers skip to check the player speed whilst they're wearing their Elytra.
If you're in 1.12, feel free to use this give-command for a book with also all gamerules, you can get it here for free: https://pastebin.com/qKn3hTLg
In 1-9-1.11, use: https://pastebin.com/NcHdEM9R
You need to insert that stacked command into a regular (orange/Impulse) command block, then trigger it.
Enjoy.

Thanks! so even with the gamerule set to false you still lose all momentum when travelling at speed with elytra, at least for me anyway

Confirmed for 1.12.1

Confirmed for 1.12.2. This happens to me on vanilla Minecraft server running on EC2 when traveling in boats.

Confirmed for 1.13-pre4

[ Confirmed for 1.13-pre5Â ]

Affects 1.13-pre6. Please keep the ticket updated.

Affects 1.13 Full Release

Can confirm for 1.13.1 for boats, unable to reproduce for max. speed spectator flying and elytra (boosted with fireworks).

Can confirm for 1.13.2 for boats. (Others not tested.)

confirmed for 1.14

Can confirm for 1.14.3-pre2, boats.

Can confirm this also happens when riding horses and can cause the player to teleport into unwanted situations. 1.14.1

Can confirm for boats and horses on my vanilla 1.14.2 server.
Â

Confirmed for 1.14.4 CraftBukkit, if that's relevant
CraftBukkit is not supported by Mojang.

confirmed for 19w35a

this also applies to horses

Can confirm for 1.16 pre release 5Â

If anything this has gotten worse with Pre7, esp with striders

this still happens in 20w27a?

Confirmed 21w14a
Boats seem to be sending a constant 80 packets to the server when moving at full speed. This seems ridiculously high when compared to other things.
EDIT: After taking this screenshot, it seems that even while NOT MOVING in a boat, it is still sending a constant 80 packets.
EDIT 2: Horses are a constant 60 packets.
EDIT 3: Minecart is a constant 40 packets.
EDIT 4: Elytra is 35 packets IF flying at max speed. Max speed of Spectator Mode is 20 packets.
[media]
This still happens in 1.17.1.

still in 1.19.4
Closing this temporarily as Awaiting Response.
If you are able to reproduce this, please provide more details.