When a game’s stats are not published, mark the field unknown—don’t fill it with a number from a different build, an unverified screenshot, or another guide. Treat every table cell as a claim, and keep its source, evidence grade, date, and applicable game version attached to it. That makes a guide useful without making uncertainty look like fact.
Why “unknown” belongs in a game stats table
A blank cell can look like an oversight; a guessed number can look authoritative. Explicitly writing “unknown” tells readers that the value was checked but could not be established from the available evidence. If the game’s developer or publisher has not announced a value, say “not announced” when that is what you can support. Do not infer a value from silence.
As an Amazon Associate I earn from qualifying purchases.
The exact-title DEV Community search result attributes a post to xhorizon and displays “Posted on Sep 11,” but the year is not visible in the result. Its excerpt proposes four evidence grades: official, confirmed, beta-observed, and unknown. Those labels are a useful starting point, not proof that any particular game stat has been verified.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →What evidence should accompany each stat?
Store a value together with enough context for another editor—or a reader—to check what it means. A practical claim record includes:
- Value: the number, text, or explicit unknown state.
- Evidence grade: for example, official, directly observed, corroborated, community-reported, or editorial calculation.
- Source: who published or observed the evidence, with its public URL and source type.
- Dates: publication date when available, plus the date the claim was checked.
- Scope: game build, platform, mode, units, and measurement definition where relevant.
- Note: what the source establishes, what it does not establish, and what event should trigger a re-check.
The WARDOGS Companion methodology distinguishes evidence categories and cautions that an official source supports what it states; it is not an independent test. Its guidance is a site-specific editorial method, not an industry-wide standard. Read the WARDOGS Companion methodology.
Keep evidence grade separate from status. A statement can come from an official source and still be stale after a patch. A current community report can remain uncorroborated. If two sources conflict, record the disagreement rather than forcing one number into the table. The GTA6 Field Guide policy uses labels such as Official, Observed, Tested, Corroborated, Community, Disputed, Stale, and Patched as an example taxonomy, not a universal standard. See the GTA6 Field Guide policy.
How to handle missing, conflicting, or older-build values
No source establishes the value
Write “unknown” or “not announced” beside the field, and state what evidence would resolve it if that would help the reader. Do not substitute a plausible estimate or a value from a different source just to complete the table.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallRank #2
Sources disagree
Preserve both reported values and label the disagreement. Before treating them as comparable, check whether they refer to the same build, platform, mode, units, and definition of the stat. If those details differ or are missing, explain that the figures cannot yet be compared directly.
The evidence is from a beta or earlier build
Label the build scope in the same place as the value. A beta observation is evidence about that beta, not automatic evidence about the current release. Do not silently relabel it as a current-game stat.
The value is calculated
Show the input values, their sources, the formula, and any assumptions. A ratio, normalized score, or ranking derived by an editor is analysis—not a game-published field. If inputs use incompatible definitions or versions, do not present the result as a fair comparison.
The evidence is a community report
Attribute the report and avoid presenting one player’s observation as representative of all players. If an editor has only read a source, do not imply personal testing. A test claim needs an identified build, conditions, protocol, run count, and a reviewable outcome.
Recommended Free Tools
Set verification thresholds for the claim
Different claims need different evidence. The WARDOGS methodology, reviewed on August 30, 2026, gives examples of minimum gates within its own process:
- For a current release date or storefront price, it specifies one current official primary source.
- For a game mechanic, it calls for an official source or direct evidence from the current build with independent corroboration.
- For a benchmark summary, it calls for at least five comparable valid observations, with sample size and range shown.
These thresholds describe that site’s stated methodology; they should not be presented as universal rules or measured industry norms. Choose a threshold that fits the claim, then make the evidence and limitations visible to readers.
A repeatable workflow for building a citation-first guide
- Define the player’s decision. Decide what question the guide should answer, such as whether a weapon’s effect is known or whether two settings can be compared.
- Register sources before drafting. Capture the source identity, URL, source type, dates, build scope, and limitations.
- Break the answer into checkable claims. Give each stat or mechanic its own record and connect it to the evidence that supports it.
- Check scope and agreement. Compare versions, platforms, modes, units, and definitions before combining values.
- Apply the relevant evidence threshold. Do not use a benchmark gate for a different kind of claim, or treat a site’s internal policy as an industry standard.
- Write only as strongly as the evidence allows. Put qualifications next to the value, not in a distant general disclaimer.
- Set a re-check trigger. Revisit patch-sensitive claims after an update, contradictory primary source, or failed reproduction.
- Make corrections legible. Provide a route for readers to report errors and show material status changes rather than silently replacing a claim.
The Game Field Guide policy describes confirmed facts as coming from first-party sources or reproducible game data, and its published policy offers an example of how to communicate evidence and corrections. Read the Game Field Guide policy.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Make comparisons readers can actually use
Compare weapons, settings, builds, or other options only when the records share a meaningful scope. State the game build, mode, platform, units, and measurement method. Choose comparison columns based on the player’s decision—such as effect, cost, availability, prerequisites, or trade-offs—and show evidence confidence alongside the values.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesIf the values use different builds or definitions, keep them separate rather than ranking them. If you calculate a score, show its inputs and formula so readers can distinguish your analysis from a stat published by the game’s developer.
Best Value
Keep the guide accurate after patches
Put a checked date on claims that can change with updates, and retain the build or storefront state they describe. When a patch, contradiction, or failed reproduction may invalidate a claim, re-check it and mark it as current, stale, patched, disputed, or otherwise appropriate to your evidence policy. Preserve the source history so readers can understand why a value changed.
No prevalence figure establishes how often game guides contain missing or invented statistics; the available policies and methodology support editorial workflow recommendations, not an industry-wide rate. A citation-first approach does not guarantee error-free data. It gives editors and readers a way to see what is known, what remains unknown, and what evidence could change the answer.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
