A player's game says they can sprint while stunned, and the host believes it

When each player's own game reports what state their character is in, a bug or a cheater can claim anything. This entry shows how the host checks every claimed change against the rules and what it answers when the claim is wrong.

Why this works

Whatever runs on a player's own device can be changed by that player, so a claim is only a request. The host holds the list of what may happen from where and keeps the rest to itself, so a lie simply gets refused.

When not to use it

Not worth it for a game among friends, a co-op game with no ranking or prizes, or one that runs only on one device. There, trusting the player is simpler, and strict checks only block honest play after a lag spike.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• A diagram of every state
• 25 lines of example code with 4 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "A player's game says they can sprint while stunned, and the host believes it" (read_entry host-validates-state-claims) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP