How I write
Editorial policy
Checked 2026-10-18
Every page is one question. I would rather ship a short verified answer than a long guess. The checked date under the title is the day I last compared the page to a source.
When I wrote the price line I did not trust a screenshot from a week ago. I called the Steam appdetails endpoint with cc=us on 18 October 2026 and read initial_formatted $19.99 and final_formatted $15.99.
What counts as a fact
A store field, an official announcement, or a first-party page can be stated as fact and linked. A community guide can be quoted as a community note. A missing pin list stays missing. I do not fill lore-map coordinates from memory.
Review totals and the live player count are snapshots. I print the day. I do not turn a one-hour player count into an all-time peak.
Corrections
Email contact@paperhead.org. If the source wins, I change the page and move the checked date. I do not quietly leave two different prices on two pages.
Questions I keep getting
Do you use reader scores as our score?
No. I quote Steam's own summary and I do not add an aggregate rating of my own.
Can a guide page invent a route?
No. If the unlock step is unpublished, the page says the step is unpublished.
Sources I used
- Steam appdetails API — US price $15.99 (list $19.99), release Oct 9, 2026
- Steam store page, PAPERHEAD — app 2680280, price and platforms rechecked 2026-10-18