Fatal Claw v0.9.269 — Bugfix Update

v0.9.269 is the second numbered bugfix build after the 2nd Expansion (v0.9.265). The official Steam notice thanked players for bug reports following the expansion. This page lists the confirmed fixes in detail. See Updates Hub for the full version history and Version 1.0 for the launch release.

Confirmed fixes

Stone Warp progression fix

Fixed an issue where progression could become blocked after using a Stone Warp without activating the required lever in Upper Elord Castle.

This was a documented progression risk in this wiki’s coverage of Upper Elord Castle. The Stone Warp system uses rest points as warp destinations. In Upper Elord Castle specifically, a lever must be activated before certain Stone Warp destinations become available. Players who warped before flipping the switch could find themselves unable to return to the section they had just left, effectively soft-locking their progression.

The fix confirms the Upper Elord Castle lever rule that this wiki has always printed: activate every lever before using Stone Warp in Upper Elord Castle. If you warped without activating the lever, the fix means a new save or a rollback to an earlier state may be necessary — the fix prevents the block from occurring going forward, but does not retroactively unblock saves already affected.

Practical advice after the fix: When you enter Upper Elord Castle, treat the lever as a mandatory step before you use Stone Warp anywhere in that region. Mark the lever room on Carox if you are in doubt.

Achievement auto-unlock fix

Fixed an issue where certain achievements were being unlocked automatically when starting the game.

This was a ghost-unlock bug. Players reported that trophies would appear on a brand-new save file before they had performed any action in the game. The affected achievements were not confirmed publicly, but the pattern was consistent: a save that had never left the first room would display achievement notifications as if certain conditions had already been met.

The fix stops the ghost-unlock behaviour from occurring on new saves going forward. If a trophy was incorrectly awarded before this patch, it will remain in your Steam profile — Steam achievements cannot be removed by the developer after they are registered. Updating to v0.9.269 or later prevents the issue from reoccurring.

If your profile has ghost achievements: Start a fresh save after updating to v0.9.269 or later. Ghost achievements from before the fix cannot be revoked, but they will not affect new saves.

Ortrinde camera fix

Fixed camera issues when using Blink combined with a downward attack during the Ortrinde encounter.

Community threads noted that Blink — Kisha’s teleport-dash ability — combined with a downward attack (pressing down while in the air to strike below) could confuse the camera in the Ortrinde fight. Ortrinde is a midgame boss encountered in Black Canyon, known for floating blades and a dedicated defeat achievement.

The combination of Blink and downward attack created a visual disconnect: Kisha would appear to teleport, the downward attack animation would play, but the camera would not track correctly, making it difficult to read Ortrinde’s response. That issue was addressed in this build.

If you experienced camera weirdness during Ortrinde’s floating-blade phase: Update to v0.9.269 or later before retrying. The fix applies to new attempts; existing attempts that were failed due to camera issues should be reattempted after updating.

What v0.9.269 is not

This is a bugfix build, not a content drop. It does not add regions, bosses, Cabitz, abilities, characters, or story content. The 1.0 launch on 26 August 2026 is the next content milestone after this patch.

Do not look to this patch for balance changes, new dialogue, new achievements, new map areas, or changes to drop rates. Bugfix patches address broken behaviour; content patches add new behaviour.

Context in version history

The confirmed version order around v0.9.269:

• v0.9.228 — February 2026, 1st Expansion: Strigine Quarry, Black Canyon, Higasha Tundra
• v0.9.236 — March 2026, first bugfix after 1st Expansion
• v0.9.265 — mid-2026, 2nd Expansion: Lower Elord Castle, Jayma’s Dungeon, Kannir Belt
• v0.9.269 — second bugfix after 2nd Expansion (this update)
• 1.0 — 26 August 2026, full release

v0.9.269 is the last numbered patch before the 1.0 launch. Post-launch hotfixes, if any, will carry new build numbers and are not covered on this page.

Reporting live bugs

This wiki is not a crash tracker. If a bug persists after v0.9.269, report it on Steam community or the official Discord. Include your build number (visible in the game’s options menu), your save file state, and steps to reproduce. Community-reported issues with clear reproduction steps are the fastest path to a fix in a live game.

The official Discord is the primary channel for bug reports that NDEV GAMES monitors. Steam community discussions are useful for tracking known issues and workarounds from other players.

What to do if you were affected by the progression block

If you used Stone Warp in Upper Elord Castle before activating the required lever and were subsequently unable to progress, options include:

1. Load a save from before the warp — if you have an earlier save file, reload it and activate the lever before warping.
2. Start a new save — if no earlier save is available, a new save will not encounter the block after updating to v0.9.269.
3. Continue and find an alternate route — some players reported that the block was not absolute and that an alternate path existed. This was not confirmed across all saves.

The fix prevents the block from occurring going forward. It does not unblock saves already affected.