DEV Community

david deng
david deng

Posted on

The hotfix with no version number: what Mortal Shell 2's November 16 patch actually fixed

On November 16, Mortal Shell 2 got its first patch since the Rotten Autumn hotfix (build 1.000.015, shipped October 23), and the announcement is titled, in full: "Hotfix: Nov 16, 2026". No version number appears anywhere in the body — nothing to type into an update check. SteamDB records build 26640691 for the window — corroboration, not a version. It hit PC, PS5, and Xbox the same day.

Third report from my crash tracker: 56 issues — 22 fixed by patches, 13 with workarounds only, 11 pending, plus a handful acknowledged, investigating, partial, or unverified — last verified November 18. The first report was a methodology, the second read October's notes; this one reads a hotfix that refuses to identify itself.

How do you even confirm you're on it?

Version-less releases break basic patch advice — update and retry — because no menu shows a number to compare. The checks are behavioral: the Mether's Pulse option is now clickable at Beacons (more below); the Rotten Autumn Halloween set dressing is gone.

What 37 lines actually contain

Transcribed in full, the notes resolve to 8 sections and 37 lines. Levels & Dungeons dominates with 10: softlocks in Winterglass Lake and the Marty's Blade dungeon, a fall through the Ashen Cathedral floor after the Sariel fight, gates that stayed shut in the Neglected Ward. Shells & Combat adds 7 — Smert's kick failing to connect after transforming back from a sheep, Gragu's punch re-equipping your melee weapon mid-punch. The rest: Tarstones & Items 4, Bosses & NPCs 3, Photo Mode 3, UI & Localization 5, Other 3.

Stability & Performance is exactly two lines: a performance improvement around coffin enemies and props, and one crash fix — "Fixed a crash that could occur when leaving an area while effects were still active." That sentence is the stability payload of a hotfix three weeks in the making: no error string, no signature, no hardware context. Next to the D3D12 dumps still on the forums, shipped-versus-diagnosable is the whole story.

Patch notes close forms, not entries

The discipline when reconciling notes against a tracker: a patch line closes the form it names, nothing more. Entry #56, Mether's Pulse upgrades, had two forms on file. Form (a): pulse efficiency upgrades silently do nothing — one player bought the upgrade five or six times and still could not refill a large health bar with all 7 charges. Form (b): the Beacon's Mether's Pulse option can be hovered but not clicked, blocking any purchase. The November 16 line reads, verbatim: "Mether Pulse can now be selected with the mouse in the beacon menu." Same entity, same menu, same failure mode — form (b) flips to fixed. Form (a) is named nowhere in the 37 lines and stays open. The entry moves to partial, stamped "form b only". Collapse it to "fixed" and every player with dead flask upgrades concludes they are patched. They are not.

A hotfix can also un-fix

The inverse belongs on the checklist too. Entry #31 is the Windows 11 launch block — "Failed to start Process… An Application Control policy has blocked this file (0x11C7)" — acknowledged since August, with a developer-recommended Smart App Control workaround. After the November 16 hotfix, one player reported the block re-appearing — a watch item, not a trend: the entry stays acknowledged, report logged, dated. Precedent: the night-mode merchant bug rode in with the October 14 stability hotfix.

What survived into November

As of the November 18 verification, the open column was untouched. The full mortal shell 2 crashing fixes tracker carries all 56 entries with status and build stamps. The short version:

The Continue-button crash is still the headline. Three independent players since late August, different hardware, same form: consistent crash on first load while continuing an existing save. The workaround that holds is a 30 FPS lock set before pressing Continue — reporter-verified, re-applied after every restart. Acknowledged in August; never named in notes since.

The night-mode Collector is still "investigating" on PC. Trading during night mode makes the merchant UI vanish and locks input — a regression that arrived with the October 14 stability hotfix. The PS5 build got its fix on October 16; PC and Xbox were promised to follow.

Also open: shell-unlock achievements that never pop (#47), trials that spawn no enemies (#48, reload workaround unconfirmed), the Smert invincibility from kick-spamming during Last Vow (#53), and the Ritual Grounds chest that stays locked after you clear the dungeon (#55).

And the tracker's newest entry is itself a crash. #58: after repeated weapon swaps — including applying Arbiter's Prize or swapping Tarstones — equipping a new weapon eventually crashes the game with an Unreal report. Three reporters, one Reddit thread, all on 1.000.015: an RTX 4070 and an RX 7900 XT, Windows 10 and 11. One player watched the odds climb the longer the inventory stayed open; another reproduced it on a second run with a fixed Tarstone sequence ending in the Veteran Axe. The developer collected mods, specs, shells, loadouts and screenshots — and could not reproduce it. The only workaround on file is one reporter's own finding, unverified: close and reopen the inventory before changing weapons. Every report predates November 16, so survival on this build is unconfirmed — hence pending, not a footnote.

The triage order stands

The phase order still holds. Thirty-second fixes first: Frame Generation off, Ray Tracing off, NVIDIA shader cache to Unlimited, FSR to TSR, verify files. Two-minute fixes next: a DDU clean driver reinstall, deleting corrupted input saves. Five-minute fixes last: shader cache clears, a static 16/32 GB page file. Stop when the crash stops. If your crash hits when equipping weapons after a long inventory session, try the inventory-reopen workaround — and report your loadout.

What an unversioned hotfix teaches

Four things generalize:

  • Date facts to builds, not announcements. With no number to anchor, the tracker's version field stays at 1.000.015 — "update to the latest patch" is advice without a target.
  • Notes close forms, not entries. Mether's Pulse leaving as "form b only" is the cleanest proof in the dataset.
  • The stability payload can be one unnamed line. 37 lines, a single crash fix, no error string. Triage from notes alone and you know less than you think.
  • Re-test old workarounds after every patch, in both directions. Old crashes can finally die; old fixes can quietly rot — see the Smart App Control watch item.

The next patch will presumably come with a number. The tracker will be watching.


This tracker is a fan-run project and is not affiliated with Cold Symmetry. Every status cites its source tier and build stamp on the tracker page.

Top comments (0)