Editorial policy
Facts are the material. The player action is the guide.
This policy explains how New Game HQ chooses facts, handles changing game information, builds original player workflows, and decides whether a page is ready to be part of the public guide library.
- Primary standard
- Useful to a player today
- Changing facts
- Dated and qualified
- Interactive pages
- Tested before release
Research order
Official status and product facts come first.
Release date, platform availability, modes, announced systems, pricing, and major update changes begin with official storefronts, developer pages, publisher pages, and patch information. Community observations can reveal a useful player question, but an unstable report is not presented as a settled answer.
Player job
Every page must answer a named problem.
Names, values, unlock conditions, item locations, and routes are useful inputs. New Game HQ reorganizes them around the next action: what to choose, where to go, what to save, what to avoid, which requirement is missing, or when to stop pushing.
| Page type | The page should let the player do |
|---|---|
| Database | Search, filter, compare, and open the next relevant action. |
| Codes | Copy exact strings, separate status, mark claimed rewards, and troubleshoot errors. |
| Walkthrough | Find the blocked step, follow a route, and recover from a wrong turn. |
| Buying guide | Compare access, price, platform features, and the live check before paying. |
| Pre-launch guide | Use confirmed information now without pretending the final build is already known. |
Originality
Public pages use New Game HQ’s own grouping and wording.
We do not copy another site’s introduction, headings, FAQ answers, screenshots, visible descriptions, table order, or complete page structure. Research facts are normalized into fields chosen for the player decision, then regrouped into a different route, filter set, warning system, and internal handoff.
- Fresh player-facing explanations.
- Original grouping by decision, route, risk, role, or stage.
- Additional fields such as next action, safe move, failure signal, or current state.
- Links to the game hub and the next same-game problem.
Working tools
A tool must change the answer or reduce repeated work.
Search, filters, saved rows, copy buttons, calculators, checklists, and reset controls are used only when they fit the player task. Core answers remain present in the page HTML so a temporary script problem does not erase the guide.
Selections, claimed codes, or saved rows persist when returning naturally helps.
Every tool has an empty state and a reset path.
Current New Game HQ tools run in the browser and do not ask for a login.
Uncertainty
Pre-launch and changing facts stay visibly bounded.
Confirmed information is separated from version-specific observations and launch checks. Balance, exact routes, prices, rotating rewards, checkpoint behavior, and platform edge cases are not extended beyond what the available information can support.
Officially announced or stable in the current product information.
Useful in the checked version and likely to need another review after a patch.
A real player question that cannot be answered finally before the release build.
Publication gate
A page enters the guide library only when the answer is usable.
- The first screen gives a direct answer, current state, or useful control.
- The page contains an original decision, route, searchable dataset, or recovery flow.
- Important changing facts have a visible date or version note.
- Same-game links show the next natural problem.
- Mobile layout, static answers, interactions, canonical URL, and structured information pass the release checks.