Methodology
Where every number here came from
One rule, applied without exception: a figure appears on this site only if it was parsed out of a response we archived. Not remembered, not recalculated from a screenshot, not carried over from another site. If we cannot show you where it came from, we do not print it.
The chain
A request is made and its bytes are written to disk with the time they arrived. A build step reads those bytes, pulls out named fields, and records for each one: the value, the field path, the URL, the capture time, the file, and that file’s SHA-256. Pages render from that record and nothing else. A separate check walks the built pages afterwards and fails the build if any visible figure is not traceable back through that chain — or if a source line shows a time that is not the time its bytes actually arrived.
That last part is not hypothetical. An early draft of this homepage had four timestamps typed in by hand. They read 01:12Z; the fetch had happened at 00:57:39Z. Every hash beside them was real. Nothing looked wrong. The check exists because of that.
What the timestamps mean
Review counts, achievement rates and prices move. Each figure carries the moment its own source was read, not the moment you loaded the page. The most recent capture behind this site is 2026-09-05T03:11:23Z. Past 36 hours the site stops describing anything as today’s and shows the date instead.
The page list
There are 10 pages: 8 for search engines and 2 marked noindex. That list lives in one file; navigation, the sitemap, robots.txt and the daily submission batch all read it, so a page cannot exist in one of them and be missing from another.
What we do not know
The most useful thing a reference can do is be specific about its own gaps. These are ours.
- Concurrent playersSteam’s player-count endpoint answers
HTTP 404for this app id. - MetacriticThe key is absent from the store response entirely.
- Exact wishlistsThe developer said “over 100,000”. That is the whole figure that exists.
- Weapon, faction and attachment dataNot in any official field. Numbers for these circulate; none came from the publisher.
- Achievement meaningsThe rates endpoint returns keys and percentages, no descriptions. We will not invent them.
- Search demandAcross every keyword on this project we have 0 guide-intent completions and no volume data at all. We do not claim anyone is searching for this.
- Anything on other storefrontsWe read one Steam listing. Statements here describe that listing, not the whole world.
- · api.steampowered.com · read 2026-09-05T03:11:16Z · sha256 8b5d8cad345317e0
Corrections
If a figure here disagrees with the source it cites, the source wins and we change the page. Mail hello@scavland.cc with the page and the field. Corrections get made, not argued.