About
What DI33 is for, who writes it, how claims are checked, and where to write when we get something wrong.
What you are looking at is a working blog. Old pieces stay up in the archive rather than quietly disappearing, including the ones that have aged badly.
DI33 began because the straight answers about video game reviews were scattered across forum threads, comment sections, and messages nobody archived. We decided to write them down properly instead.
There is no subscription, no newsletter upsell and no course. If that changes we will announce it on this page before anywhere else.
What we do not do is predict outcomes. Nothing about video game reviews works that way, and pages that pretend otherwise are selling something.
One article, one topic. It keeps the category pages usable, and in practice games are where most readers end up.
Every article carries the name of the person who wrote it, and every name links to a page listing everything else they have written.
Hannah Cole, Editor and strategy reviewer. Hannah reviews strategy and story-heavy games, finishes everything she writes up, and keeps a notebook of every run that went wrong.
Marcus Reyes, Multiplayer and competitive reviewer. Marcus spent years grinding ranked ladders before deciding he liked explaining games more than climbing them.
Priya Nair, Indie and co-op reviewer. Priya plays most co-op games with her partner on the couch and judges them the same way, through long ordinary evenings.
People ask about the name. There is rarely a good story behind a domain, and there is not one here either. DI33 was available, it was short enough to say out loud, and it has been the name long enough now that changing it would be more confusing than keeping it.
We write from notes taken while doing the thing, not from a summary of other summaries. Where we are unsure, the page says so in plain words.
We buy what we write about. It is slower, it is more expensive, and it is the only arrangement that lets us say a thing was not worth it.
If you want the mechanics rather than the summary, the editorial policy has them, including what we refuse to publish.
Corrections go to [email protected]. Quote the sentence rather than describing it. We would rather log a visible correction than edit a page and hope nobody noticed, and the contact page explains the rest.
