Mortal Shell II - Beta Patch Notes Current

Branch boundary: public test notes can be ahead of the default release branch. Match the build number before relying on a fix.

Mortal Shell 2 Beta Patch Notes: Current Public Test Changes

The latest documented public test sequence improves crashes, camera and targeting, UI, localization, Gloom recovery, Seal behavior, and boss balance, with build 87133 changing Lady of the Woods and Tar Golem stun behavior.

Build 87133 highlights

Lady of the Woods balance modifications and changed stun behavior for her and Tar Golem. Localization and text improvements. PC interface, audio, collision, Seal stun, shutdown, and video crash fixes. A beehive was removed from the Lady of the Woods arena and dialogue skipping was adjusted.

Hotfix 86724 highlights

Target Steering modes: Default, Light, and Off. Cyclic inventory navigation and a sprint camera-shake slider. Improvements to localization and Gloom-location behavior. Work to reduce patch sizes, plus attack lock-on and crash fixes.

Hotfix 86328 highlights

An option to disable rumble. Gloom drop and retrieval improvements. New Axe & Dagger and Crossbow locations. Infinite Seal and crossbow adjustments. Fixes targeting common crashes, camera collision, health bars, Lute behavior, collisions, and Tar Golem achievement reliability.

How to use these notes

Match the build number first. The public test branch can be ahead of the default branch, so a fix listed here may not yet exist in the version you launched.

Sources used for this guide

Community update Public test branch and hotfix 86328 Community update Public test hotfix 86724 Community update Public test build 87133

Frequently asked questions

No. The current open beta is on PC through Steam; the full game is announced for PC, PlayStation 5, and Xbox Series X|S.

Read the public-test sequence as build history

The three build numbers describe an ordered Open Beta test sequence, not a cumulative guarantee for the retail game. Start by matching the application and branch, then locate the exact build named by the report. A change listed in 87133 can supersede behavior from 86328, while the default beta branch may have received the work on a different schedule. Without that match, a patch bullet is only a lead for investigation.

Separate confirmation from resemblance. If a note mentions crashes, camera collision, targeting, UI, or a boss, it does not prove every later report using the same noun has the same cause. Reproduce the symptom, record the action and location, and compare the same sequence before and after the relevant build. Mark a companion issue reconciled only when the tested result and the source claim align.

For the released application, use current patch notes and official support evidence. Keep these beta notes available because they explain why an old guide or video may behave differently, but do not relabel them release fixes. A dated historical record is more accurate than silently discarding the branch boundary or promising that a beta correction survived unchanged.

Link a route or known-issue record only when the patch note names a matching symptom or encounter. Broadly attaching every crash or balance bullet to every page would create false relationships and make later reconciliation harder.

A precise build citation keeps that relationship reviewable after the beta branch closes.