Big Walk blog

Checking your computer before playing? Read Can Big Walk run with 8 GB RAM? for Windows and Mac requirements, memory examples and player reports.

This is the long-form half of the site. The walkthrough pages answer where a puzzle is and how to solve it; they are built to be skimmed while four people stand around a lever, so they stay short. The blog is the other kind of writing: one question at a time, taken apart slowly enough that you can check the working yourself, and kept after the answer settles so you can see what changed.

The house rules are the ones the sources page already describes. Every figure carries its source and the date it was read. Claims arrive in order — claim, evidence, source, context — never a number floating free of where it came from. When we do our own arithmetic we show the sum, not just the result, so you can disagree with a specific step instead of accepting or rejecting the whole conclusion. When two sources disagree, both stay on the page: picking a winner and announcing it as the answer is exactly the habit this blog exists to avoid.

The first entry takes the question every new group asks before installing: how long does Big Walk take? There is no official figure anywhere in the developer's own materials, the published estimates span a wide band, and almost none of them say what they counted. So instead of repeating one more range, we added up the entries in our walkthrough library that carry real timings, set that result beside the numbers already circulating, and wrote down exactly why they disagree. If you only want something to put on a calendar, the planning section at the end turns the whole argument into evenings.