Spielerando

I rewrote chapter two: which earlier tester comments still apply?

Playtest notes pile up while the story keeps changing, and a complaint about a scene that no longer exists wastes your time. This entry marks each comment as still valid, outdated or orphaned, without throwing away comments over a fixed typo.

Why this works

A comment is a reaction to words that were on the screen at that time. If the words are mostly the same, the reaction still applies. If they changed a lot, the reaction belongs to a scene that no longer exists, so test again before trusting it.

When not to use it

Words are not the whole scene: a comment about a hard puzzle or a missing item can survive a full rewrite of the text, and a tiny change can break a scene. Let a person decide on comments about the situation rather than the wording.

In the full entry

  • What to build, step by step
  • Starting values and the reason for each
  • 3 common mistakes and the fix
  • 36 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 "I rewrote chapter two: which earlier tester comments still apply?" (read_entry feedback-gone-stale-after-a-rewrite) 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