These are the only ways for a server to manipulate the client in any way similar to what you have described. Usually these are not employed intentionally, as it’s quite scummy to do. Three, the client will crash (an uncaught exception, usually), causing the client to close. Two, the client will freeze completely (a deadlock, usually). One, the client will simply disconnect from the server (corrupted NBT or JSON, usually). Thirdly, the server is able to, in multiple ways, send corrupted packets that cause the Minecraft client to crash completely. Mining fatigue effect can also do similar things with block breaking. The slowness effect can also be used to completely freeze player movement, but more “smooth” than what movement resetting will do. Most hackers probably would be unaffected by this so it is not employed outside of mini games usually however this with a combination of movement calculation checks and movement resetting, the first one I mentioned, would allow the server to enforce your player to be slower than normal as a punishment for cheating. Secondly, the server is able to send a Slowness potion effect - which will “slow down” the player but this effect is only enforced client side.

This is capable of completely stopping movement of a player and freezing them, or to teleport them back to a location before a violation. Firstly, the server is able to decline movement packets and reset your location, as it ultimately has control of where your player is located.

Wurst client 1.11