[Vince]

If it is a sequence of checkpoints, like a race, I would compare the time the player entered the current checkpoint with the time they entered the previous checkpoint and make a decision based off of that. From what I've encountered, most cheaters spam the button until they reach the second-to-last last checkpoint. Then they wait, only to finish right as the first legit player comes in sight in order not to immediately alert the admins. But if the race has more than three checkpoints this system should cover that.

On the other hand, if it concerns a single checkpoint I really see no efficient way to do this. I would probably continuously store the player's last known position. Should they enter the checkpoint, I would calculate the distance between the checkpoint and the last known position and make a decision based off the distance overcome within the set time frame.