Hellraiser sewer ladder bug: what’s confirmed and which workarounds remain unverified

Reports checked October 8, 1:23 p.m. PDT

Kingy’s review of Game progression block by bugs… and Can Not Progress BUG found 15 distinct reporting accounts. Seven report eventually getting past the ladder; eight have not posted a resolution in those threads. Accounts posting in both threads are counted once. These are player reports, not a measured failure rate or proof that the eight remaining players are still blocked.

Where the reports agree

The repeated location is the sewer-exit ladder after the club, around the first encounter with the vendor. The first thread describes the “Get to safety” objective. Reports describe falling through the ground, remaining beneath the level, or falling continuously. Returning to an earlier checkpoint or restarting has not helped everyone. Location reports, second thread.

The earlier snapshot contained eight distinct reporters, three accounts of passing the ladder and five without a reported resolution. Four new reporters appeared between 11:00 and 11:24 a.m. Vancouver time: Mr Blue, Zeb89, Steve and Revenholm. Later posts and an edited success report changed that tally. The current 15-account count preserves that growth without counting repeated comments as additional players.

Seven accounts now describe getting through: Katostrofic, LizzardKing, Wizard In Black, Revenholm, Mack, WhitedogAwesome and A Bad Monk. The other eight are johnny0010luka, Mr Blue, Steve, Zeb89, JD_84, lightbender, King and Angeluz. A successful crossing establishes that a player progressed; it does not isolate what caused the next attempt to work. First thread, second thread, including later replies.

Why the suggested settings remain unverified

See the 60fps success report, failure despite suggested settings, edited 30fps report and low/windowed report.

None of these settings should be presented as a dependable repair. Changing several settings and then crossing the ladder leaves the cause uncertain. The available posts also do not establish an HDD-versus-SSD cause, an affected build range, or whether consoles share the fault.

Preserve the checkpoint and record a useful reproduction

Keep your existing progress. Before testing, make a separate backup of the relevant save/checkpoint using a method you have verified for your installation. Kingy has not verified this game’s save-file location or backup-and-restore procedure. Do not delete your only save or start over on the assumption that it is permanently damaged.

A useful reproduction clip should:

This is a suggested evidence protocol. Kingy has not reproduced the bug or recorded a gameplay clip.

The developer-marked Saber Help account asked for a video and a support report. Use Saber’s Hellraiser support form to provide your evidence. That reply establishes a request to investigate; it does not announce a fix or explain the cause.

1. Identify the retail PC/Steam installation and installed build/version. If the build is absent from the game menu, capture the installed Steam build information separately.
2. Show Frame Generation, display mode, frame cap, graphics preset, resolution and upscaling settings before the attempt. Include GPU, driver, storage type and any mods in the accompanying report.
3. Begin from the backed-up checkpoint, show the approach to the sewer-exit ladder, and continue through the fall or successful exit without cutting away from the transition.
4. Record the result of each attempt. For a settings comparison, change one variable at a time and document which checkpoint was loaded.

The September demo guide has a different scope

Kingy’s demo input, Journal and puzzle display guide covers the September 21 demo patch. Its input, Journal, puzzle-shadow and environmental fixes do not establish that this retail ladder issue has been fixed.

The Steam news feed showed the October 8 launch announcement and the older demo patch notes when checked. Kingy did not find a retail sewer-ladder fix announcement in the reviewed feed or the two discussion threads. Future updates should identify the exact patched build and distinguish a developer’s patch claim from players’ results on that build.

October 8, 1:23 p.m. PDT: Reviewed both threads, including the second thread’s two pages. Expanded the earlier eight-account snapshot to 15 reporters, seven reported crossings and eight without a posted resolution. Added the conflicting 30fps and low/windowed anecdotes. No reliable workaround, verified root cause or permanent save-corruption evidence established.