[00] About
About Scholarly Gamers
Scholarly Gamers is a video game publication for players who finish a game and keep thinking about it.
The idea is simple. Games are played with the hands, but they are also built from ideas: about freedom and control, about history, about what a machine is and what a person owes it. A review can tell you whether the combat feels good. It can also notice what the combat is for.
So the site reads games closely. Reviews judge the craft. Features follow a single question through a game or a genre, whether that is how NieR: Automata turns its save file into an argument or why so many studios keep building dystopias. Tech Talks go under the hood of the PC, because the machine a game runs on shapes how it is experienced.
The tone is curious rather than academic. Nothing here requires a philosophy degree, and nothing assumes that a game has to be serious to be worth thinking about. A boulder punched in a volcano gets the same attention as Nietzsche.
- [01]
Reviews
Reviews of console and PC games that look at how a game plays and what it is reaching for. No scores: each review closes on who the game is for.
- [02]
Features
Essays on philosophy, design, history and culture. One question per piece, followed through the games themselves.
- [03]
Tech Talks
The hardware behind play, from case airflow and cooling to the physics of heat, explained so the reasoning outlasts the part numbers.
- [04]
News
Releases, events, awards and industry changes, each dated and kept as it stood on the day it was reported.
[05] How it works
How the site works
How reviews are written
Every review names the exact platform the game was played on, because a game can run very differently on a base console, an enhanced one and a PC. Performance notes, load times and frame rate comments refer to that machine only.
The review itself weighs the same things each time: how the game controls, how it runs on that platform, how its pacing holds up over hours rather than minutes, and whether its story and structure deliver what they set out to do. Those are the parts of a game that stay true after release, which is why the verdict describes them rather than giving a number.
Prices are launch prices in US dollars on the review date. They are kept as a record of what the game cost at release, so a reader can judge the verdict against the price it was written for.
How features are chosen
A feature starts with a question that a game raises and does not answer itself: why a save file can carry an argument, why players keep returning to worlds that have already ended, what a high score is worth when nobody can check it. The piece then follows that question through what happens on screen.
Older games get the same treatment as new ones. A fighting game from the 1990s can explain a mechanic in a current one, and a history of backwards compatibility explains why a console generation is remembered the way it is.
Dates and corrections
Every piece carries its original date and describes the situation on that day. News items record what was announced, reviews record the version that was played, and neither is quietly rewritten when a patch or a price cut arrives later.
When a fact in a piece is wrong, it is corrected in the text itself. A corrected detail replaces the wrong one rather than sitting in a note at the bottom of the page.
Pictures
Article images are illustrations made for the site, not screenshots or publisher artwork. Each one carries a small AI label in its corner, and its caption describes the scene it shows, so a picture is never mistaken for a photograph of the game or the event itself. Screens, logos and characters from the games are described in the text instead.
[06] Questions
Questions readers ask
Is Scholarly Gamers an academic site?
No. The name points to a way of reading games, not to a university. The writing is curious and plain, and nothing on the site needs a degree to follow: an argument about NieR is made from the game itself, not from footnotes.
What kind of reader is the site for?
Players who finish a game and want to talk about it afterwards: why a mechanic works, what a story was getting at, how an old genre led to a new one, or why a PC runs hot.
Why do some pieces look back at older games?
Because history explains the present. Features on the early arcades, backwards compatibility and what counts as "retro" put current games in context, and older fighting games still teach habits that carry over.