A level I made by hand has no exit or two start points

When levels are typed as text pictures, one slipped character is enough to make a level impossible, and you only notice when a player writes in. Here is a checker your AI can run over the whole pack, with messages that point at the exact level and line.

Why this works

Mistakes typed into text levels are small and look alike: one wrong character, one short row. A machine finds them reliably, while your eyes skip over them after the tenth level. Checking the whole pack before every release catches this class of slip all at once.

When not to use it

Skip it for a handful of levels you play through yourself before release, and for levels made in an editor that cannot produce a bad shape. The check only proves the shape is sound; whether a level is fun or can be solved needs a separate look.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 47 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 "A level I made by hand has no exit or two start points" (read_entry level-file-check-before-shipping-a-puzzle-pack) 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