Nobody has published a recovery. Two players are hard-blocked, no developer has replied, neither established wiki covers it, and no reload procedure exists — which also means nobody has confirmed the run is lost.
Nobody has published a recovery. Two players hit this independently, no developer has replied to either, no guide site covers it, and no reload-from-an-earlier-save procedure has been posted anywhere — which also means nobody has established that the run is actually lost.
Where this is being asked · Steam Community, in a thread where two players describe the same thing happening to them in the opening sequence. The thread has no developer reply and no answer from anyone else.
Evidence
The answer, broken into claims
A grade describes sourcing, not truth. Inferred means we concluded it and the reasoning is shown; unverified means someone asserted it and nobody stands behind it.
CorroboratedTurning the wheel and leaving the area shuts the hatch and leaves the wheel permanently non-interactive.
Two players reporting it independently in the same Steam thread, read 2026-08-05. Nobody has contradicted them.
InferredNo recovery procedure has been published anywhere.
Our check on 5 August 2026 of the thread itself, both established wikis, the publisher’s news hub and the pinned developer Q&A. Every one of them came back empty.
InferredNobody has established that the run is lost either.
The absence runs in both directions. No player has reported testing an earlier save and failing, so "unrecoverable" is as unsourced as "recoverable".
§01
What the blocker is
It sits in the first quest most players do, which is why it matters more than a one-thread bug usually would.
Turning the wheel opens a hatch down into the subcity.
If you leave the area before going through the hatch, the hatch is shut when you come back.
The wheel is then permanently non-interactive. There is no second prompt and no reported alternative route.
Two players describe this independently in the same thread. Neither got a reply.
§02
What was checked, and what came back
This is the part that makes the page worth publishing. A gap is only a finding if you can see where it was looked for.
The thread itself: two reports, no workaround posted, no developer reply.
The publisher’s Steam news hub: seven posts, the most recent being the availability announcement naming version 1.0.6. No patch notes and no known-issues list among them.
The pinned developer Q&A thread, opened 3 August with a promise to fill it out over the first day: still at zero replies on 5 August.
Game8’s walkthrough hub, the most advanced chapter walkthrough in the niche at chapter 7 of 13: no page on this.
Fextralife: no chapter walkthrough at all, and no page covering the sequence.
§03
The four things nobody has answered
Every one of these is a question a stuck player is actually asking, and not one of them has a published answer. Whether loading an earlier save puts you back in front of an openable hatch. Whether the game keeps a save far enough back to try. Whether another route into the subcity exists. Whether the state is tied to a specific order of actions, which would at least tell the next player what to avoid. Nobody has tested any of it in public, so we are not going to tell you which of them is true.
§04
The only thing here that is actually actionable
Prevention, and it is worth stating plainly because it costs nothing: if you turn the wheel, go through the hatch in the same visit. That is not a fix for anyone already blocked — it is the one instruction the reports support. If you are already stuck, the publisher’s only published contact route is a support ticket at support.fictions.com. Nobody has reported using it for this specific problem, so we cannot tell you whether it leads anywhere.
Expiry condition
What would have to change for this answer to be wrong
An answer about a live-service game without this is an answer with a hidden expiry date.
A developer replies in the thread, a patch makes the wheel interactive again, or one player posts that loading an earlier save put them back in front of an openable hatch and a second player confirms it. Any one of those converts this page from a gap into an answer.
Citations
Every source, with its date
A complaint posted before 30 July 2026 describes the playtest, not the game you bought, and a source whose publication date nobody captured cannot show that it postdates launch either. Both are flagged rather than quietly mixed in.
That two players independently report turning the wheel, leaving the area, and returning to a shut hatch and a permanently non-interactive wheel — and that the thread contains no workaround and no developer reply. Read 2026-08-05; the thread carries no absolute post stamp, so this is the date we read it.
The sequence this blocker sits inside: the route to the Foreman underground in Sub-City 1. Cited to place the wheel, not for anything about the blocker itself. Read 2026-08-05.
That the pinned developer Q&A, opened 3 August with a promise to be filled out over the first day, still showed zero replies on 5 August. Cited for the absence of any developer channel that has addressed this, not for anything it contains.
That the publisher’s own news feed carries seven posts, the latest being the availability announcement naming version 1.0.6, and that none of them is a patch note or a known-issues list. Cited for what the publisher has not published. Read 2026-08-05.
That the most advanced chapter walkthrough in this niche — Game8’s, which has reached chapter 7 of 13 — carries no page on this blocker. Evidence about Game8’s coverage, not about the game. Read 2026-08-05.
That the largest wiki in the niche publishes no chapter walkthrough at all and no page covering this sequence, so it has nothing to say about the blocker either. Read 2026-08-05.
Related questions
Nobody has published a fix, and nobody has published a confirmation that it is unfixable. Two players are blocked, the thread has no developer reply, and no guide site covers it.
