A two-player game without a host feels delayed or keeps correcting itself

When two players run the same game directly against each other, waiting for the friend's key press makes everything sluggish, while guessing and being wrong makes things jump. The way out is to guess, keep going, and quietly redo the last moments when the truth arrives. Here is what to keep and how to find where the guess went wrong.

Why this works

Waiting for the truth makes everything slow, and people mostly keep doing what they just did. So a guess is right most of the time, and when it is wrong you only need to replay the short stretch since the last certain moment.

When not to use it

Do not use it when the game is heavy to replay or when a wrong guess has lasting effects that cannot be undone, like a score or a death shown to everyone. Wait for the friend's input there, or use a host.

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
• 40 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 two-player game without a host feels delayed or keeps correcting itself" (read_entry online-redo-the-last-moments-when-a-friend-input-arrives) 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