Home / THRESHOLD / Game history

THRESHOLD / GAME HISTORY

THRESHOLD Question House Softlock: What the Old-Save Advice Actually Covered

THRESHOLD’s developer recommended restarting for one player using an old November save. Later reports described the question house locking on fresh playthroughs, so that advice cannot be treated as a universal explanation or repair.

By Patchlo Editorial Desk · Published October 31, 2026 · Sources checked October 31, 2026

Short answer

THRESHOLD’s developer recommended restarting for one player using an old November save. Later reports described the question house locking on fresh playthroughs, so that advice cannot be treated as a universal explanation or repair.

Scope: Steam discussion beginning in December 2024, with developer replies and later 2025 player reports. No final universal fix version was verified.

Industrial passage in THRESHOLD
Industrial passage in THRESHOLD. Publisher-provided Steam gameplay image, used for game context; it does not reproduce the reported bug. Image source ↗

A question outside, no answers inside

Paco’s report describes particles outside the house signaling a question, followed by entering and finding no dialogue choices. The door then prevented departure. The useful symptom is that missing interaction, rather than a generic claim that the game is broken.

Record the actions before the lock

The developer later asked about previous questions, the last action and whether the player was loading an older save. Those details are part of diagnosing the case.

  1. Note the question or event immediately before entering.
  2. Enter the question house when the outside effect appears.
  3. Record whether choices appear and whether the door can be used.
  4. Include the installed build and whether this was a new run or a loaded older file.

Repeatedly loading the same checkpoint is not proof that its state has changed. Retain the affected file if you want support to examine that sequence.

The restart recommendation had a specific scope

In January 2025, Heeeeedi said the file dated from November. PATALOON replied that many fixes had happened since then and recommended starting again for that case. It is reasonable to report that exchange. It is not reasonable to turn it into a claim that old saves explain every question-house failure.

Later reports keep the conclusion narrower

Onecreator later reported reaching a similar block twice during a new playthrough and followed up afterward. Those are player reports, not Patchlo tests or proof of the current build’s code behavior. The checked thread does not establish a final universal repair version. Keep this issue separate from a different bridge complaint in the same discussion; combining their triggers would give readers a procedure that no single report actually supports.

Join the conversation

Have a question, correction or a different take? Share it below. Comments appear immediately after submission.

3–2,000 characters. Your name and comment will be public. Please avoid personal contact details, advertising and abuse. Comment policy & privacy

Reader comments

Loading comments…