Tell us what we missed

Four of the six amendments on this sheet came from readers rather than from us, which is the strongest argument we have for keeping this page prominent. If a teardown describes a system incorrectly, or if a patch has changed something we measured, this is where to say so.

Write to the desk

05.1 · Form

Read by: All six of us, weekly
Typical reply: Four to nine days
Corrections: Answered first, always
Post: Toffee Factory, NE1 2DF

We read everything and reply to most things. What we cannot do is take review requests for unreleased games, or promise coverage of anything — three teardowns a month across six part-time people does not leave room for commitments.

Your name

Email address

What is this about

Which machine were you playing on

Useful for stability disagreements. Ours are measured on the weakest supported machine.

Your message

Minimum twenty characters. There is no maximum — Marged once received two thousand words on junction throughput and read all of it.

I understand my message will be read by the six people listed on the bench sheet, and that if it results in an amendment the change will be logged publicly. My name will not be published unless I say so.

Fields marked are required.

This form does not send anything. The site is a set of static pages with no server behind it, so the button validates what you have typed and confirms it locally. For a message that actually reaches us, write to [email protected] or post to the address in the footer.

Amendment log

05.2 · Six entries

Every change made to a teardown after publication appears here with a date, a description and the origin of the correction. Nothing is edited silently. Where a change moved one of the four bars, the old figure and the new one are both given.

Amendments to published teardowns, most recent first
Date	Teardown	What changed	Origin
18 Jul 2026	Transit builder	Stability raised from 34 to 41 after a patch fixed the save corruption we recorded at large network sizes. The original figure and the reason for the change are both noted in the teardown.	Our own retest
02 Jul 2026	Flight simulation	Access section rewritten. The original text described the controller-only provision as absent when it exists but is buried three menus deep. Bar unchanged at 29 — the provision is present but not findable.	Reader, Cardiff
11 Jun 2026	Tactics campaign	The eleven per cent upgrade figure was originally given as fourteen per cent, a spreadsheet error affecting the last nine hours of logged data. Endurance bar dropped from 79 to 74 as a result.	Reader, Leeds
29 May 2026	Stealth systems	Corrected the description of guard memory decay, which persists for ninety seconds rather than sixty. Does not change the verdict but does change one of the two examples used to illustrate it.	Reader, Glasgow
14 Apr 2026	Survival loop	Added a paragraph noting that the hunger system behaves differently on the handheld build, which we had not tested at the time of publication. Structurally unsound mark stands.	Reader, Belfast
21 Aug 2025	First strategy piece	Withdrawn in full and replaced with a note explaining why. Nine thousand words of diary that never described a system. It remains our most-read page, which we try not to think about.	Our own decision

Where the desk is

05.3 · Address

Building: Toffee Factory, first floor
Nearest metro: Manors, about eight minutes on foot
Visitors: By arrangement only

The Toffee Factory sits on Lower Steenbergs Yard in the Ouseburn valley, a short walk downhill from Manors metro station. It is a restored Victorian works that now houses small creative studios, and our room is on the first floor at the back, overlooking the water.

The Cutaway
Toffee Factory
Lower Steenbergs Yard
Ouseburn
Newcastle upon Tyne
NE1 2DF
United Kingdom

There is no reception and nobody sits at the desk during the day, because all six of us are at other jobs. Post is collected twice a week. If you want to visit, write first and one of us will meet you — usually on a Thursday evening, which is when the wall gets rearranged.