Refuse a dialogue answer the player was never offered

A modified or lagging game client can send an answer that was hidden, belongs to someone else, was already used or comes from a scene that is over, and the story jumps to a place it should not. Here is the list of things to check, and the order that does not leak secrets.

Why this works

Never trust what the other side says it saw. The server remembers exactly what it offered to whom, so a reply can only be judged against that record, and identifying options by name rather than position keeps the record true when the list changes.

When not to use it

Skip it in a game for one person on their own device, where nobody gains by cheating and the extra checks only add upkeep. Keep the checks for anything shared, ranked or paid for.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• A diagram of every state
• 23 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 "Refuse a dialogue answer the player was never offered" (read_entry online-validate-dialogue-answer-against-offer) 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