GameThrum publishes useful, source-grounded coverage for players. Accuracy and decision value take priority over speed, volume, or a dramatic verdict.
Our editorial principles
- Answer the reader’s actual question. We choose topics that help someone decide, configure, understand, or complete something.
- Separate facts from experience. Store listings, developer posts, patch notes, and platform documentation can establish stated facts. They cannot establish how a game performs or feels in our tests.
- Show testing limits. A review identifies platform, version/build when available, test dates, play time, progress, hardware context, and any modes or features not tested.
- Prefer primary sources. We cite official game pages, developer or publisher materials, platform documentation, and direct patch notes before secondary summaries.
- Do not invent authority. We do not fabricate credentials, interviews, access, consensus, or first-hand play.
- Correct the record. Material errors receive visible corrections or update notes under our Corrections Policy.
Article labels
- Review: contains a documented hands-on evaluation and verdict.
- Tested Guide: answers a focused question with a reproducible test record.
- Game Profile: summarizes verified public information; it may include a clearly labeled test section only after play.
- News/Update: reports a dated change using attributable sources.
- Explainer: clarifies a system or term and states whether its conclusions were tested or source-derived.
We do not convert a Game Profile into a Review merely by adding opinion to public materials.
Byline and accountability
Content is published under GameThrum Editorial Team. The byline is organizational, not a claim that every team member worked on every page. Each internal record must identify the researcher, tester, writer, editor, sources, and approvals. Public pages disclose the information readers need to assess the work without publishing unnecessary personal data.
Reviews and scores
A score, if used, summarizes the written evaluation; it does not replace it. Scores require hands-on testing, an explicit completion state, and editorial approval. We do not score an unreleased game, a trailer, a demo as though it were the final release, or a game we have not played. Early Access and review-in-progress coverage must be labeled.
Updating coverage
We update when a patch, platform release, server state, or corrected fact materially changes the answer. A changed date does not by itself prove meaningful review. The update note should say what changed and whether we retested it.
Reader and developer input
Readers and developers may send corrections or supporting evidence. Submissions do not guarantee a change or favorable coverage. We verify material independently where practical and disclose source limitations.