Slow Playthrough Quarterly
Games played to the end
A game is not a product to be assessed in the first weekend. It is a place you spend time in, and the interesting things about spending time somewhere become visible only after the novelty has worn off. Every essay here was written by somebody who played to the end and then waited a while before writing.
Somewhere around hour ninety, the quests stop being tasks and start being routines. This is usually described as a failure of design. After two hundred hours and a great many notes, I want to argue it is the point, and that we have no critical language for it.
Nobody who says a game is too hard means the inputs are too demanding. They mean the game is asking for more of their week than they had budgeted. Once the complaint is restated that way, most of the noise around difficulty settings resolves into a question about respect.
The most common failure in a long game is not a bad ending but an ending at all. Four hundred hours of accumulated habit is interrupted by twenty minutes of resolution, and the resolution is asked to carry a weight nothing that short could bear.
Every writer here keeps a paper log. Not for accuracy, though it helps, but because the act of writing a sentence about what just happened is the smallest available unit of critical attention, and it changes what you notice next.
I loaded a character I no longer remembered building and found a plan I could not reconstruct. The game had preserved my intentions perfectly and my reasons not at all.
Three weeks of walking through an open landscape with no objective marker, and the surprising discovery that boredom is a texture rather than an absence.
A number is a summary, and the whole purpose of an eight-thousand-word essay is to resist being summarised. What we publish instead is the hour count.
By the time we publish, the discourse has finished and the patches have landed. This is the least commercially sensible decision we make and the one we defend most easily.