I described a rule in plain words and I want to be sure the game does exactly that

Rules with a few yes-or-no conditions are where an AI most often gets the grouping wrong, and a quick test of one case will not show it. This entry gives your AI a way to try every combination against your own words and print the ones where they disagree.

Why this works

With a handful of yes-or-no inputs the number of cases is small enough to try all of them. A mismatch is then a concrete combination the person can judge, which settles who is right faster than arguing about wording.

When not to use it

With more than about a dozen conditions the cases double each time and become unreadable. Split the rule into smaller named rules and check each on its own.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 21 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 "I described a rule in plain words and I want to be sure the game does exactly that" (read_entry rpg-rule-versus-code-all-cases) 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