A fast double tap on Buy must not charge twice, but two real purchases must

Phones send taps faster than screens update, so a button can fire twice before it greys out, and the player loses coins for one item. Blocking all repeat taps hurts honest buyers of stackable goods. This entry separates the two cases and keeps the balance exact.

Why this works

Two taps on one dialog are one wish, and two dialogs are two wishes. Giving each offer its own name and refusing a name that already succeeded stops the double charge, while the check and the payment happen in one step.

When not to use it

This protects a purchase inside your own game. Real money goes through a payment provider, which has its own safeguards, and you should rely on those and the receipt it gives, not on a rule you wrote.

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
• 28 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 fast double tap on Buy must not charge twice, but two real purchases must" (read_entry double-tap-buy-charges-once) 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