Your Player Didn't Mean To Metagame. Your Notes Made It Easy.

Your Player Didn't Mean To Metagame. Your Notes Made It Easy.

A player's character acts on something they couldn't possibly know, and it's not cheating -- it's bookkeeping. Here's the two-log habit that keeps party knowledge and GM secrets from bleeding into each other.

Your player's character walks up to the cultist leader and immediately goes for the throat -- correctly guessing she's secretly the vampire from three sessions back, in a scene her character wasn't even in. Nobody cheated. Nobody's trying to ruin the reveal. The player just remembered something true, and their character had no way to know it.

Most tables call this metagaming and treat it like a discipline problem -- ask players to "just forget" what they know out of character, or glare until they self-correct. That mostly doesn't work, because you're asking someone to un-know something, and human memory doesn't have a delete key. The actual problem is upstream of the player: it's that the GM is usually keeping party knowledge and GM-only secrets in the same head, and often the same messy notes doc, with nothing marking where the wall is supposed to be.

If your session notes read like "the party learns the mayor is corrupt" right next to "the mayor is secretly working for the cult, reveal in session 9," you've built the leak yourself. There's no separation to police, because there was never a separation on the page.

The fix is two logs instead of one. A party knowledge log holds only what characters have actually learned in-fiction -- something they witnessed, were told, or found -- and it only gets an entry the moment that happens at the table, not when you decide it as the GM three weeks earlier. A GM-only log holds everything you know that hasn't been revealed yet: the mayor's real allegiance, the vampire's identity, the trap under the floor. Same campaign, same brain, but now there's an actual line between "the party knows this" and "I know this," and you can check which side of it a piece of information is on before it accidentally comes out of a player's mouth.

The part that makes this actually work instead of becoming one more doc nobody updates: tag entries in the party knowledge log with who was present when it was learned. Not every table runs with a full roster every session, and a player who missed the reveal shouldn't get it for free through someone else's recap at the start of next session -- that's its own quiet metagaming leak, just table-to-table instead of GM-to-player. A one-line "present: Mara, Dex, Theo" next to each entry gives you something to actually check against when a player brings up a fact their character wasn't around for.

This is exactly the kind of thing GameMasterCraft's session and campaign notes are built to hold without turning into a second job -- NPCs, factions, and now knowledge state, all living in the same connected workspace instead of three separate documents you have to cross-reference by memory.

None of this requires catching anyone or having an awkward conversation about cheating. It just means the wall between what your players know and what you know exists somewhere other than your own recollection at 11 PM on a Tuesday. Do that, and the reveal you've been building for six sessions actually lands as a reveal -- because nobody had a way to see it coming except the character who earned it.

Comments (0)

More from the Blog

Ready to create something?

Subscribe to an individual app or get the full GameMaster Studio.