The error I pasted to my AI was five hundred lines long and it missed the point
A long list of technical lines hides the three that tell where your own story code went wrong. This entry shrinks such a list to the message, the few lines from your files, and a count where the same line repeats, before it goes to your AI.
Why this works
Most of a long error list describes machinery you did not write and cannot change. The useful part is the message and the few places in your own files, and a line repeating over and over is itself the clue that something calls itself.
When not to use it
Do not trim when the fault lies in a tool or add-on you installed, because its lines are exactly what you filtered away. Then paste the full list, or at least the part around the first error, and let the AI judge.
In the full entry
- What to build, step by step
- Starting values and the reason for each
- 4 common mistakes and the fix
- 16 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 I pasted to my AI was five hundred lines long and it missed the point" (read_entry trim-an-error-trace-before-pasting) 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