setVelocity bug in 1.21.10

[justin0-0]

Expected behavior

The method setVelocity does not work like before for players. In 1.21.8 the method worked like usual but in 1.21.10 newest Build (#100) the player sometimes doesn't get launched or launched extremly far into the air. I test it with this setup with the paper 1.21.10 and 1.21.8 api aswell as on the paper 1.21.8 server and lower and on the 1.21.10 newest server build. On other pcs its the same problem with the same plugin so i would think its a spigot/paper bug. Somehow the method works well for values of 1-10 in the y direction but for 100 it does not work anymore.

@EventHandler
public void hit(BlockPlaceEvent event) {
    System.out.println("1");
    event.getPlayer().setVelocity(new Vector(0, 100 ,0));
}

Observed/Actual behavior

...

Steps/models to reproduce

...

Plugin and Datapack List

...

Paper version

1.21.10 build #100

Other

No response

[Malfrador]

Can reproduce, though I am not entirely sure what is going wrong here and if this is something that should be fixed.

It seems to somehow run into the "Moved too quickly" check, despite that really being intended for movements initiated by the client. However, 100 is also just a very excessive velocity and it does work correctly with more sane values such as 25.

Using the PlayerFailMoveEvent and allowing the movement there does work as a workaround too.
Though ideally, the server setting velocity shouldn't trigger this in the first place. Looking at it with a packet logger doesn't reveal anything odd, the order of set_entity_motion, move_player generally seems correct.

Not entirely sure if we can fix this, and if we want to fix this if it only happens as excessively high velocities.

[Lulu13022002]

Mojang changed the max cap from 3.9 to 1.7179869183E10, so before your velocity in Y was capped, now it's effectively 100 which result in you hitting the limit.