Context Rot
You've probably had a session where the GM starts strong but slowly gets worse. It forgets a rule you set up. It contradicts something it said an hour ago. It starts giving generic responses instead of ones that feel grounded in your world. This is context rot.
What's Happening
Your Game Master has a limited working memory. Every time it responds, it reads through everything loaded into that memory: your pinned files, partial file summaries, the conversation history, and any files it looked up along the way. The more stuff in there, the harder it is to focus.
Context rot happens when that working memory fills up with low-value information, pushing out or drowning the things that actually matter.
There are a few ways this creeps in:
Too much pinned content. If you've pinned 20 files of rules, worldbuilding notes, and character backstories, the GM is reading a short novel before every single response. It can't give equal attention to all of it. The critical instructions ("never kill a player character without warning") get the same weight as the nice-to-haves ("the tavern keeper has a lisp"), and both suffer.
Redundant or contradictory instructions. When multiple pinned files cover overlapping ground, the GM has to reconcile them. If your "Combat Rules" file says one thing about initiative and your "House Rules" file says something slightly different, the GM may split the difference or pick one unpredictably.
Vague, wordy content. A pinned file that's 2,000 words of atmospheric prose takes up the same space as 2,000 words of clear, actionable rules, but delivers a fraction of the value. The GM doesn't need to be inspired by your writing. It needs to know what to do.
The Signs
You might be dealing with context rot if:
- The GM "forgets" rules you've set up, especially ones from pinned files
- Responses start feeling generic or repetitive as a session goes on
- The GM contradicts earlier decisions or established facts
- You notice the GM ignoring some pinned content while following other pinned content
- The tone or personality drifts from what you defined
How to Fight It
The core principle is simple: less is more. A focused, well-organized set of context will always outperform a bloated one.
Audit your pinned files regularly. Read through everything you've pinned and ask: does the GM need this in every single response? If the answer is "sometimes" or "it's nice to have," move it to Partial. If it's reference material, make it Searchable.
Keep pinned files short and direct. Write for function, not flavor. Bullet points beat paragraphs. "Roll for initiative when combat starts. Players go first on ties." beats a three-paragraph explanation of your initiative philosophy.
Remove duplication. If two files say similar things, combine them or cut one. Every time the GM reads the same instruction twice, that's space wasted and a potential source of contradiction.
Use Partial for world content. Your NPCs, locations, and factions don't need to be pinned. Set them to Partial so the GM knows they exist and can look them up when relevant.
The Pinned File Checklist
Before pinning a file, run through these questions:
- Does the GM need this for every response? If it's situational, it should be Partial or Searchable.
- Is it under 200 words? Long pinned files dilute everything else. If it can't be short, consider splitting it into a short pinned summary and a longer Searchable reference.
- Is it actionable? Pinned content should tell the GM what to do, not provide background reading. Lore belongs in Partial or Searchable files.
- Does it overlap with another pinned file? Consolidate or remove the duplicate.
- When did you last update it? Outdated instructions are worse than no instructions. They actively mislead the GM.
If a file doesn't pass all five, it probably shouldn't be pinned. Move it to Partial and write a clear title and description so the GM can still find it.
For more on how to structure your content across the three visibility levels, see Context Visibility and Progressive Disclosure.