My log is far longer than my AI can read, which lines should I keep

Pasting the whole log either gets cut off at the wrong end or drowns the one useful line. This entry picks lines in order of importance until a size limit is reached, and marks every gap so the AI knows lines are missing.

Why this works

The lines that explain a crash cluster around the first error, while the start is routine noise. Keeping lines by importance, and marking where lines were left out, gives the AI the story without false neighbours.

When not to use it

Not suited when the cause is far from any error line, such as slowness that builds up quietly or a problem that leaves no error at all. There the whole timeline matters; send a smaller log from a shorter session.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 42 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 log is far longer than my AI can read, which lines should I keep" (read_entry cut-a-long-log-to-fit-the-ai) 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