I live in a quiet suburb outside Seattle. Not because I work in games anymore—I don’t. But because I spent long enough inside those buildings to know what the design docs don’t tell you. Now I just watch from the edge of the parking lot.
This is a notebook about the systems underneath role-playing games: the numbers, timings, thresholds, and feedback loops that quietly decide whether a world feels alive. The numbers are evidence. The experience is the conclusion.
The Gap Between the Spreadsheet and the Controller
I used to think the most important part of my job was the feature list. The elegant stamina curve. The clean aggro radius. The carefully tuned animation priority that made combat feel “fair.” I spent years adjusting variables until the spreadsheets looked balanced and the playtest notes stopped screaming.
Then I left the room where the tuning happened, sat down with a controller as an ordinary player, and discovered something uncomfortable: many of the systems I had helped shape still felt opaque, arbitrary, or strangely heavy in ways the documentation never predicted.
That gap is why this site exists.
What the Design Docs Never Predicted
When a horse in The Witcher 3 suddenly feels trustworthy instead of floaty, something specific has changed in the steering response, the camera lag, or the way the animal recovers from a collision. When an Elden Ring boss begins to feel oppressive the moment you step inside a certain distance, the pressure is not just “difficulty”—it is geometry, line-of-sight rules, and recovery windows working together. When a day in Stardew Valley feels productive rather than punishing even though the clock is relentless, the comfort is engineered through pacing, interruption design, and the careful management of attention.
I used to believe more feedback always meant better feedback. I used to treat player reports of “weight” or “drag” as soft language that needed to be translated into harder metrics. I was wrong often enough that the only honest response left is to dig.
The Method I Now Follow
Every major investigation on this site follows the same five-part structure.
1. The Sensation
Start with the sensation a player actually reports—tension, immersion, friction, safety, the sudden urge to quit or the quiet decision to stay one more hour.
2. The Suspected Machinery
Isolate the variables that could produce it: distances, timings, probabilities, animation priorities, information delays, resource rates.
3. The Field Test
Test them under controlled conditions, on specific platforms and versions, and record the limits of what can actually be observed.
4. The Competing Explanation
Consider at least one plausible alternative, including the possibility that the effect is emergent rather than intentionally authored.
5. The Conclusion
State clearly what the evidence supports, what remains uncertain, and why the felt experience changes.
What This Site Will Not Do
I will not rank games. I will not score stories or graphics. I will not pretend every mechanic was deliberate or that my former colleagues’ offhand remarks constitute proof. Former colleagues remain unnamed. Their stories are texture at best, hypotheses at worst.
The only authority here is what can be measured, timed, compared, and returned to a concrete moment of play.
The Daily Texture of the Work
There is a gray cat who interrupts this work at irregular intervals. There is a noisy city coffee shop where I watch people navigate systems they do not realize are systems, and a quieter suburban café where the actual writing happens.
Mornings are for drafting. Afternoons are for reading and playing. Nights are for sorting captures, timings, and half-formed ideas that may not survive contact with the next play session.
I left the industry because I wanted distance, not access. Distance makes certain things clearer. You stop defending the design document and start asking what the player’s body and attention are actually responding to. You stop assuming the system is hiding and begin treating it as a language most reviews never bother to translate.
Closing the First Entry
This site is the record of that translation.
If you have ever finished a session and thought, “Something about that fight / that ride / that day cycle felt different, but I can’t name why,” you already speak the language. I’m just trying to write the grammar down.
The numbers are evidence.
The experience is the conclusion.
Let’s dig.
No entries yet — sign the first.