Update policy

The date changes only when the player answer is reviewed.

New Game HQ revisits pages when a release, patch, platform change, balance update, broken interaction, or correction can change the route a player is following.

Every guide
Visible update date
Pre-launch pages
Release-day review
Tool changes
Interaction retest
01

Review triggers

We review the route when the game changes the decision.

TriggerWhat is reviewed
Release or major patchStatus, unlocks, values, routes, and guide handoffs affected by the build.
Platform or price changeAvailability, subscription access, store facts, device support, and purchase guidance.
Balance or reward changeRankings, investment advice, material routes, and any tool filter built on the old value.
Broken interactionSearch, filter, save, copy, reset, empty states, and mobile behavior.
Player correctionThe reported fact and every visible recommendation that depends on it.
02

Visible update date

The page date represents a real check.

A page receives a new visible date after the affected answer, dataset, route, or interaction has been reviewed. Small typography changes, rewritten transitions, or a date-only edit do not count as a current game check.

Content check

The direct answer and affected rows still match the current state.

Route check

The recommended next action still follows from the data.

Page check

Links, controls, mobile layout, and structured information still agree.

03

Pre-launch to launch

Launch checks are resolved, retained, or removed.

Preparation and comparison pages can remain useful after release, but each field marked for launch review must be checked against the live product. A preview assumption is not silently converted into a final claim.

  1. Confirm the release state.Update the hub, date, platforms, and official availability.
  2. Test the open questions.Resolve co-op, controls, routes, progression, or feature edge cases where possible.
  3. Keep uncertainty honest.Leave a question open when the launch build still does not provide a stable answer.
  4. Update connected pages.Review the hub, focused guide, navigation label, and related recommendation together.
04

Data and tools

A changed row can change more than one result.

When a unit, trait, material, code, class, platform, or route changes, the review includes the visible row and any filter, shortlist, recommendation, saved state label, or structured list that uses it.

  • Default result count and filter counts.
  • Search terms and empty state.
  • Saved or claimed state after refresh.
  • Reset behavior and browser storage version.
  • Static answer available without the interaction script.
05

Changed or retired facts

Old information does not stay prominent for history’s sake.

Expired codes, removed features, superseded routes, and changed platform offers are separated from active answers. When an old state still prevents confusion, it may remain clearly labeled; otherwise it is removed from the primary workflow.

Players can report a stale value or route through the corrections page.