The error report names a dozen files and I do not know which is mine

Most lines in a crash report point into the tools your game uses, not into your own code, and the real culprit is a few lines down. This helper picks out the lines that point into your own files, in order, so you hand your AI the right place.

Why this works

A crash is reported where it happened, which is often inside a library that was handed something wrong. The first line that belongs to you is the call that did it, so that is where the AI should look.

When not to use it

When the very first line of the report is in your own file, that is simply the answer. When every line is in a library, the problem is likely in how it is loaded, not in your code.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 40 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 "The error report names a dozen files and I do not know which is mine" (read_entry work-act-which-error-line-is-mine) 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