Match a watcher's scribbled notes to what happened in the game

Someone sits next to the tester with a stopwatch and writes "gasped at 2:05". Later you want to know which scene that was. This entry fixes the clocks that never start together and decides when a note belongs to an event and when it belongs to nothing.

Why this works

Two clocks that started at different moments disagree by a fixed amount, so one shared moment lets you correct every note at once. A note describes what just happened, never what is about to, which is why it can only look backwards.

When not to use it

Skip it when the game itself records the tester's comments, for example by voice during play, because then the clock is already shared. Also skip it for notes about the mood of the whole session, which belong to no single moment.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 27 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 "Match a watcher's scribbled notes to what happened in the game" (read_entry observer-notes-matched-to-game-events) 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