Audit a recipe list for loops, twins and dead ends before players find them

When a puzzle game has dozens of recipes written over several evenings, mistakes creep in: two recipes with the same ingredients, an item that needs itself, or a made item that nothing ever uses. These are invisible while playing and obvious to a checker. This entry finds all three and says which recipes are to blame.

Why this works

Mistakes in a recipe list are patterns in the data, so a machine can find them faster and more reliably than any player. Running the same checks every time a recipe changes catches a fresh mistake while it is still one edit old and easy to trace.

When not to use it

It cannot judge whether a recipe is fun, fair in effort or sensible in story, and some dead ends are deliberate rewards. Do not take a clean report as a sign of a good puzzle; still have people play it.

In the full entry

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

Say this to your AI

Use the Spielerando entry "Audit a recipe list for loops, twins and dead ends before players find them" (read_entry puzzle-recipe-list-audit) 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