How we test

A guide is only useful if you can check it.

New Game HQ writes about games that change. A route that worked in one build can fail after a patch, and a value that looks authoritative on a database page can be wrong for your platform. This page explains what we check before a page becomes public, what we record, and what we still ask you to confirm in your own game.

First check
Official game or store source
Second check
Current build on a named platform
Recorded on the page
Version, platform, and check date
When unsure
Say so and leave the claim out
01

What “checked” means

Checked means we looked at the current game, not only at another article.

A New Game HQ page is checked when the claim on the page has been compared with a source a player can also inspect: the game menu, the current build on a named platform, an official patch note, an official store listing, or the developer’s own announcement. A claim that only repeats another guide, a video description, or an unsourced comment is not treated as checked.

We separate three states on purpose:

  • Confirmed. The fact is visible in the current game, an official store page, or an official patch note, and the page records when it was seen.
  • Version-specific. The fact is true for the build and platform named on the page, and may change after a patch or on another platform.
  • Open check. The page explains what to look at, but does not pretend the answer is settled. An open check is a real answer when the honest answer is “confirm this on your screen first.”

This is why some pages use cautious language. Caution is not a substitute for content; it is a label on a specific claim. A page that only says “results may vary” without telling you what to do next does not meet our standard.

02

The four checks

Every public page has to survive four questions.

1. Is there a named player task? The page must answer a question a player can recognize: which upgrade to craft first, why a delivery route stops, which mission is blocking progress, which code is still active, or how to read a stat that looks contradictory. A page built around a keyword rather than a task does not pass.

2. Is the answer in the page, not only in a tool? Search, filters, and planners are useful, but the core answer must still be present when the interactive layer is not used. A reader should be able to find the recommendation, the condition, and the failure case in the text.

3. Does the page change a decision? A useful page changes what the player does next: which route to take, which material to farm, which setting to change, or when to stop spending. A page that only restates the menu does not pass.

4. Is the boundary visible? The page must say which build, platform, or date the answer belongs to, and what the reader should check if their screen does not match. A claim without a boundary is treated as unfinished.

03

What we record

Version, platform, date, and the step that proved the answer.

For a guide, we record the platform used for the check, the build or version shown in the game, the date of the check, and the step that produced the result. For a database row, we record the field values, the source type, and the last check date. For a tool, we record the input cases that were tested and the result the tool returned.

We do not treat a screenshot alone as proof. A screenshot is useful when it shows the menu, value, or state that the page is talking about, and when the caption says what to look at. An unlabeled image is decoration, not evidence.

Build

The version string or patch number visible in the game or on the store page at the time of the check.

Platform

The console, PC storefront, or mobile client used. Platform differences are called out when they change the answer.

Method

The smallest repeatable action that produced the result, such as a fresh save, one route, or the same input twice.

Limit

What the check did not cover: another mode, a later boss, a different difficulty, or a value that the menu does not expose.

04

What counts as evidence

The best evidence is a step another player can repeat.

We prefer evidence in this order:

  1. The current game screen. A menu, tooltip, quest log, map marker, or result screen that another player can open in the same build.
  2. An official patch note or store page. A developer or platform statement that names the change, the date, and the affected platform.
  3. A repeatable observation. The same action produces the same result twice, with the same inputs, on the platform named on the page.
  4. A bounded community report. A player report that is clearly labeled as reported and is not presented as a confirmed mechanic.

A single unlabeled video, a comment, or a screenshot without context can suggest a question. It cannot settle one. When the only available evidence is a community report, the page says so instead of upgrading the claim.

05

What we do not claim

We do not fill a gap with a confident sentence.

We do not publish guessed drop rates, hidden formulas, exact damage values that the game does not show, or a “best” build that depends on a mode we did not test. We do not turn an unknown value into zero, and we do not present a pre-launch plan as a confirmed route.

We also do not claim that a page is complete. A guide can cover the first ten hours and still leave the endgame open. The page should say what it covers, so you can decide whether it answers your question before you spend an evening on it.

If a detail cannot be confirmed, the page uses one of three honest outcomes: it names the open question, it gives the smallest safe test, or it leaves the claim out. A shorter page with a clear boundary is better than a longer page with an invented number.

06

When a patch lands

A patch turns a confirmed fact into a check again.

Balance changes, new systems, platform fixes, and seasonal events can invalidate a route without changing the page’s title. When a game changes, we review the pages that depend on the changed system first: progression gates, material sources, build recommendations, code boards, and any page that quotes a number.

The update policy is simple. The page keeps its original route, adds the current version and date, and marks the part that changed. If the old answer is still useful in an older build, the page says which build it belongs to. If the old answer is now wrong, it is replaced rather than left beside the new one.

You can see the same discipline in the update notes on a game hub: the hub shows the current status and the last check date, while a focused page shows the date of its own check.

07

Reproduce a check

You should be able to test the answer in a few minutes.

Before you trust a route, open the page’s version and platform line. Then reproduce the smallest step the page describes, not the whole route. If the first step matches, continue. If it does not, stop and check the failure note before changing several variables at once.

  • Confirm the build and platform named on the page.
  • Open the same menu or location the page uses as its first check.
  • Repeat one action with the same inputs before changing gear, difficulty, or route.
  • If the result differs, note the platform, build, and the first step that diverged, then send a correction.

This is also the fastest way to tell whether a page is wrong for your version or wrong for everyone. A platform-specific difference is a boundary; a step that fails on the same build is a correction.

08

Corrections

A specific correction is more useful than a rating.

If a page is wrong, send the page URL, the platform and build, the step that failed, and what you saw instead. A screenshot or a short clip helps when it shows the menu or result. You do not need to write a full report; the first failed step is enough to start.

Corrections are reviewed against the current build. When a correction is accepted, the page is updated and the check date changes. When the report cannot be reproduced, the page keeps the original answer and the open question is recorded instead of being replaced by a guess.

Use the corrections page or email corrections@newgamehq.com. For privacy, copyright, or accessibility requests, the contact page has the right route.

09

Who does the work

A small editorial team, with automation used for the repetitive parts.

New Game HQ is written and maintained by its editorial team. The same team selects the player question, checks the source, writes the page, and handles corrections. We publish under a shared site byline because the site, not a single contributor, is responsible for keeping a page current.

Automation helps with the repetitive work: collecting official facts, normalizing record fields, checking links, and flagging pages that have not been reviewed since a patch. It does not decide whether a page is useful, and it does not invent a value that the game does not show. A page is published only after an editor has reviewed its answer, boundary, and next step.

If you want to know how a specific page was checked, the page’s update date and the method above are the starting point. If that is not enough, ask through the correction route and include the page URL.