Make sure a purchase or door opening is not done twice when the message repeats

Important messages are sent again when no answer comes back, so the other side may receive the same one two or three times. Without care, a player pays twice or a chest gives its content again. Here is how to recognise repeats cheaply, what to do with a message from long ago, and why the answer must still be sent.

Why this works

A repeat usually means the answer got lost, not that the player asked twice. Remembering which messages are already done lets you do the work once and still reply every time, so the sender can stop asking.

When not to use it

Skip it for messages that do no harm when done twice, such as a position update or setting a value to a fixed number: do them again and move on. The memory is needed only for things that add up, like a payment.

In the full entry

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

Say this to your AI

Use the Spielerando entry "Make sure a purchase or door opening is not done twice when the message repeats" (read_entry online-handle-the-same-message-twice) 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