My AI said it finished the boss fight but parts of it do nothing

AIs often leave empty stand-ins for the parts they meant to do later and still report the job as done. This helper scans the code for those stand-ins, notes, empty bodies and functions that always give the same answer, and lists them by line.

Why this works

A stand-in looks right to the eye and passes a quick play, but it removes the behaviour you asked for. Four patterns catch almost all of them, and a list by line turns a vague doubt into a short checklist.

When not to use it

Some empty pieces are on purpose, like a do-nothing handler or a piece that really always returns false. Treat the list as questions for the AI to answer, not as a verdict on faults.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 32 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 "My AI said it finished the boss fight but parts of it do nothing" (read_entry work-act-ai-left-placeholders-behind) 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