Write the player's diary so it never knows more than the player does
A journal that fills itself in is a lovely way to tell a story, until it mentions a name or a place the player has not met yet. Here is how to build entries from what was really discovered, on the day it was discovered, with the right words for the moment.
Why this works
A diary is a record, so it must say what was known when it was written. An entry from the day she was a stranger keeps saying stranger, even after the name is learned, or the diary gives away what the player has not earned.
When not to use it
Skip it when the journal is a guide that should grow wiser with the player, such as a field book that corrects itself. There, rewriting old pages is the point; just say clearly that they were updated.
In the full entry
- What to build, step by step
- Starting values and the reason for each
- 3 common mistakes and the fix
- A diagram of every state
- 22 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 "Write the player's diary so it never knows more than the player does" (read_entry journal-only-knows-what-player-found) 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