Discussion

Half Salvation Stone bug - partial fix in 1.0.27, still open at 1.0.66

The Half Salvation Stone Steam bug on Fatal Claw: partial fix in 1.0.27, replayed Sep 4, and still unfixed as of 1.0.66 four patches later.

Half Salvation Stone bug - partial fix in 1.0.27, still open at 1.0.66 discussion artwork from Fatal Claw

This thread tracks the Half Salvation Stone bug report. A partial fix shipped in 1.0.27 Hotfix, and a Sep 4 replay by CaesiumFox showed the fix was incomplete. Four patches have shipped since then — 1.0.41, 1.0.54, 1.0.58, and 1.0.66 — and none of their patch notes mention this bug. As of 1.0.66 the case is open, not pending. The workaround is still to reload from the last save.

Reopened report — Sep 4 (CaesiumFox)

A second player report landed on 2026-09-04 at 03:16 (Beijing time) in a new thread (Half Salvation Stone bug (CaesiumFox), 0 replies as of this writing). The reproduction matches the original report almost line-for-line:

  • Equipping Cabitz while holding the Half Salvation Stone then picking up the 6th Adrian’s Marble triggers the softlock.
  • Result: screen goes black, player input is locked, save flag is now in a stuck state.

The structural overlap with the original report (same equipment stack, same pickup sequence, same end state) is high enough that this is more likely a 1.0.27-fix-incomplete than a separate bug class. NDEV has not yet responded to the Sep 4 thread.

Where the case stands now (updated 2026-10-12):

Updating past 1.0.27 no longer resolves this. The original guidance was to move to 1.0.38 Hotfix and re-test, on the reasonable assumption that a patch shipping the same day as the replay report would address it. It did not. 1.0.41, 1.0.54, 1.0.58, and 1.0.66 have all shipped without naming this bug, and 1.0.66 — the build that did fix two other hard progression gates, the Moss Cave swimming gate and the Jack Combinator drop — is silent on it.

That silence is informative. 1.0.66 shows NDEV will ship a fix for a softlock that blocks progression, so the absence of this bug from that list is a stronger signal than any single unanswered forum thread.

  • If you are stuck, reload from the most recent auto-save before the trigger point. This has been the workaround since 1.0.27 and remains correct.
  • If you can reproduce on 1.0.66, post it on the Bug Report forum with your build version and reproduction steps. A fresh report on a current build is more actionable than the September threads, and NDEV has not replied to either of those.
  • Do not expect a fix in the next patch. If one appears, we will close the case here.

What players are reporting

The Half Salvation Stone is an in-game item tied to a quest step in the post-Yamator’s wings progression arc. Players report the related interaction fails to trigger under a specific condition (the original post is single-line; the bug context is implied by the thread title and the dev acknowledgment landing within twelve hours).

The wiki does not have a step-by-step walkthrough of every Salvation Stone trigger point, because the steps vary by region. What we do have: the broad-stroke walkthrough hub, the ability system guide, and the per-region pages like Kannir Sanctuary and Origin Laboratory where Salvation Stone mechanics surface.

What “fix queued” meant, and what 1.0.27 changed

NDEV’s reply pattern on the forum is consistent:

  • If they can’t reproduce, they ask for a save file.
  • If they can, they say “thanks, fix in upcoming update.”
  • If a hotfix is urgent (story-blocking, softlock), they push it inside 24–48 hours — that is the pattern 1.0 Pre-Release Hotfix followed for the Sorron’s Archive door softlock.

This thread got the middle reply, and NDEV held to the pattern. The fix landed in 1.0.27 Hotfix on 2026-09-02, three days after the dev reply. Players currently stuck on the older build should update to 1.0.27 to clear it.

Adjacent bugs worth knowing about (same forum, last 24h)

While reading this thread we also spotted three other fresh reports in the same window — they are not NDEV-acknowledged yet, but they cluster together and players tend to hit them around the same point in the late-game arc:

None of these have an NDEV reply yet, but they are all in the same post-1.0 cluster.

How to recognize if you’ve hit this, and what to do now

If you are past Yamator’s wings, have found a Half Salvation Stone pickup, and the follow-up interaction (NPC, environment trigger, or save flag) refuses to fire — that is consistent with this report.

Before the patch (pre-1.0.27): the recommended workaround was to reload from the most recent auto-save before the trigger point, or drop a save file in the original thread so NDEV could replicate.

As of 1.0.66: the original case filed by 6ssd was closed by the 1.0.27 patch, but the Sep 4 replay by CaesiumFox is still reproducible on current builds. Four patches have passed without a mention. If you hit it on 1.0.66, post a fresh thread with your build version rather than appending to the September ones — NDEV replied to the original within twelve hours but has not replied to the replay.