This site's position is simple: every number, coordinate and rule has to point at a one-line source, and anything that came from us is written as "our inference". Listed below are all the sources, the grading standard, and when the data was collected.
Last collected:2026-09-14
Source tiers
The tiers are not there to look rigorous. They are there so you know when to trust a line and when to go check it yourself.
Official data API4 sources
Valve's own statistics endpoint. Machine-readable, never hand-edited, and the only source of every completion-rate figure here.
Developer site3 sources
Pages House House / Panic maintain themselves. Final say on rules, version history and player guidance lives here.
Developer announcements1 sources
Patch notes and posts written by the team itself and pushed through the Steam news feed. Patch information is taken from nowhere else.
Player community1 sources
Guides written by players. These are first-hand play sessions, but each one is one person on one run, so we use them as a lead to cross-check rather than as a conclusion.
Press coverage1 sources
Background and corroboration only. Never used for a coordinate, a solution or a number.
·Real worldwide completion rates for all 12 achievements
·The drop at every step of the progress funnel
·How rare the true ending and the full collection actually are
This endpoint returns Valve's worldwide owner completion rates to one decimal place. Every percentage on this site is taken straight from it, with no processing beyond rounding.
Steam achievement list (names, descriptions, official icons)
The endpoint only returns machine names (apiname), not display names. We matched the two by both meaning and the fact that the two lists sit in exactly the same order, and both checks point at the same mapping.
The version history the developer maintains themselves, and the official FAQ explicitly points here as the single source for patch notes. More complete than the Steam announcements - some small versions only left a record on the site.
About 23,000 characters of first-party Q&A covering players, online play, chat, troubleshooting and accessibility. The official rules decoded page on this site is built directly on that text.
·Tested experience with connection and save problems
Community guides are valuable for detail and risky for singularity. Any coordinate that disagrees with a second source is labelled "community field report" on this site rather than stated as fact.
Press coverage
Steam news aggregate (press reviews and sales coverage)
Background only. Never used for a coordinate, a solution or a number.
Which player guides we actually read
There are around thirty Big Walk guides in the Steam Community hub. Saying "we consulted thirty guides" is meaningless, because they are not one quality tier: some are an author writing down their own playthrough, failures and timings included, and some are one article translated into ten languages and stamped "2026 update". So we list every guide we genuinely read, with the tier we gave it and what exactly we took from it.
Field report3 guides
The author played it through and wrote the process down, failures and time spent included. The most trustworthy tier we have.
Quick reference4 guides
Organised reference material. Specific, but with no account of how anything was found. Usable, and we flag it as a single source.
Derivative content1 guides
The same article published in several languages in bulk, or essentially a promotion for a map site or a paid tool. Corroboration only.
Field report3 guides
Big Walk - Challenge [Purple] Puzzles Advice / Tips
·Challenge-by-challenge tactics for all seven purple challenges
·The concrete body-as-encoder scheme used for the nine speakers
·Real timings and real failure points on the golf ball route
The author states which ones they cleared first try and which took repeated attempts, and leaves room for "correct me if I misremembered". That is exactly what a field report should look like.
·The key chain: each cutting station marks the key with an arrow to the next one
·What walkie-talkies do, and the one-at-a-time trade-off
·Which transport each of the four towers unlocks
The content is precise, but the page itself is the documentation for an interactive map site (lootmap.gg), so it sits in reference rather than field report.
·The rough districts for seven radio stations and three megaphone mounts
·The trade-off of the portable radio occupying your hand slot
The same text published separately in Chinese, English, Portuguese, German, Spanish and more, each titled "2026 update", and it states outright that its source is an interactive map site. The location wording is vague - "southern mountaintop" - so we use it only to confirm counts like 7 stations and 3 megaphone mounts, never for a precise coordinate.
Two things we could not do, stated here: one player-made gesture alphabet exists only as images, so we could not transcribe the individual movements and borrowed only the design idea; and every one of these guides is one group's one experience, so any conclusion backed by a single source is labelled single-source in the text rather than written up as a game rule.
What we deliberately mark as uncertain
The easiest mistake a guide site makes is writing uncertain things in the same voice as certain ones. Here is everything on this site that has no primary source and is only our inference, collected in one place:
Which achievement belongs to which tower
The developers never say which achievement maps to which tower. Where one matches directly we say so; the rest are labelled "tower placement inferred".
The real item names behind the redactions in patch notes
The official notes describe function and never name the item. We give our inference with its basis, split into "inference" and "guess" tiers, and never write it as a confirmed answer.
The equation "Big Makeover = 100%"
The official description only says Get shiny. Treating it as the full-collection marker is community consensus, and we label it as community consensus.
Whether 1.4.7 is the shipping build
Reached by reading backwards from 1.4.8 calling itself the first patch after release. The developers never state it.
Some coordinates for the yellow, blue and black towers
No cross-checkable source exists, so we leave them blank and say plainly on the relevant pages that this is not an omission.
A few puzzles have outline-level information only
Those tutorial pages are marked "in progress", and we do not fill the steps with speculation.
How we verify
If a machine can read it, we do not copy it second-hand.Completion rates, review counts and release data all come straight from official endpoints, never from a third party's summary of them.
At least two sources before we write "verified".A coordinate given by one community guide is labelled a community field report, not a settled fact.
When sources disagree, we say they disagree.For example two sources describe the black tower's position differently, so we list both instead of picking one and calling it the answer.
Original strings are preserved.The coordinate finder shows the source's own wording, including hedges like "community guide" and "another source says", so you can judge the confidence yourself.
This is an unofficial fan-made guide site with no affiliation to House House or Panic. Copyright in the game name, achievement icons and store assets belongs to their respective owners. If you hold those rights and want something changed here, contact details are in the footer.
Let Microsoft Clarity record anonymous sessions and heat maps so we can improve the guides and the tools. Site analytics only, never advertising. Choosing "Not now" still leaves the whole site usable.