Count "clear 30 red gems" once per gem, also in cascades and special pieces

A quest that counts matches instead of pieces pays out too early with crossing lines and too late with chain reactions. Here is what to count, what a piece that turns into a power-up does to the number, and how to make the total match what the player saw.

Why this works

Every piece is its own thing with its own identity, so a quest can ask which pieces have gone instead of how many events happened. A thing can only leave the board once, however many lines it sat in, and that makes double counting impossible.

When not to use it

Skip it when the goal is about the moves themselves, such as making a set number of matches or a big combo. Then the match is the thing to count, and counting pieces would reward the wrong play.

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
• 22 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 "Count "clear 30 red gems" once per gem, also in cascades and special pieces" (read_entry match-three-quest-counts-each-gem-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