You should only punish the player if they trip these checks often within a short time period. This can be because the client has high ping or because the server isn’t checking often enough. Are they walking faster than their walkspeed? Have they been doing it for a few seconds?.Are they hovering in the air without a negative Y velocity? Have they been doing it for a few seconds?.You can calculate their velocity using (current pos - last pos)/frame time, then….Is their current position too high from their position when they were last on the ground? If so, they’re jumping higher than possible for their JumpPower.

Log when they’re on the ground using raycasts.

100 studs), such that they must have teleported?

Did they move impossibly far between the last and current frame (e.g.

Did they walk through a CanCollide = true part between the last frame and current frame? (use raycasts).

Here are some checks you can do using the last frame position and current position: The most reliable way to combat the listed exploits – which are all character movement exploits – is to check the HumanoidRootPart’s position on the server every frame. Fun fact: the server listens for the client to say it touched parts in some cases, so exploiters can spoof touched events! You need to do magnitude checks for those on the server. They can even report a Velocity of 0 while they’re moving, report a WalkSpeed of 16 while using 200, or report touching parts they aren’t touching.

In theory, an exploiter can change everything about their client, including removing and replacing your exploit-checking code but reporting to the server that everything is OK. Furthermore, they need to check only the position of the player, as almost everything else can be spoofed by the exploiter. To combat exploiting, all of your checks need to be on the server.

Easy noclip roblox