Mortal Shell II Database
Support-status guide

Mortal Shell II Bug Reports & Known Issues

Use the official Mortal Shell II reporting path, check current known-issue categories, and keep first checks separate from promised fixes.

Report and triage3–8 minutesOfficial Steam thread and latest patch checked October 16, 2026
Quick answer

Your route in one minute

Report Mortal Shell II problems in the Steam Bug Reports forum. The current developer list includes players being unable to trade with the Collector or Night Merchant; it does not publish a universal fix. Before posting a PC issue, the developer asks players to restart the game, verify files, restart Steam, and avoid running as Administrator. Those are first checks, not guarantees for every crash, missing item, input problem, achievement, or save.

Step by step

Follow the route

  1. 1

    Check the current known-issues categories

    The developer thread currently names an inability to trade with the Collector or Night Merchant, alongside encounter-state, chest or puzzle, achievement, interaction or input, and save concerns. Use that wording to decide whether your report belongs to an already tracked category.

    Tip: A matching category does not mean every symptom has the same cause or remedy.

  2. 2

    Try the listed first checks on PC

    Restart the game, verify game files, restart Steam, and avoid running as Administrator. Treat these as low-risk checks before reporting, rather than as a cure for every issue.

  3. 3

    Capture the state before changing it

    Take a screenshot or video when the screen, map, location, or interaction state explains the problem. Record your platform, installed version, and the last action that preceded it.

  4. 4

    Write a report another player can recognize

    Name the task, location, boss, item, choice, or input involved and say whether the issue repeats after a restart. For PC reports, include relevant hardware and settings context.

  5. 5

    Keep saves and achievement claims carefully bounded

    Back up a save before changing files. The official thread offers limited issue-specific suggestions, but player reports do not prove a shared recovery route.

    Warning: Do not rely on a community-reported fix as a guarantee for a missing save or progression state.

  6. 6

    Compare a dated patch with the exact symptom

    Use the October 13 hotfix page for named changes. It lists Black Needle and infused-stone interaction fixes, Mether's Breath warning-flow fixes, and other specific changes; a patch note should not be used as proof that an unrelated achievement, progression, or save problem is resolved.

If progress stalls

Recover without restarting the route

  • • If interaction UI disappears or inputs stop responding, the official thread lists restarting as a first check while the cause is investigated.
  • • For a missing save or altered settings, make a backup before changing files and re-check the current official wording.
  • • For a blocked achievement or progression route, do not assume a community workaround applies to your platform or save.
Decision errors

Check these before committing

  • • Treating a player report as proof of the cause or a universal fix
  • • Assuming a named patch resolved every achievement, item, or save problem
  • • Changing save files before making a backup
  • • Posting without platform, version, location, or reproduction details
Why this game is different

The mechanic behind the route

A useful bug report is a route through uncertainty: it captures enough context to distinguish a current official category from a player-specific symptom without turning a temporary workaround into a guaranteed repair.

Common mistakes

What goes wrong and how to fix it

Calling every symptom a confirmed known issue

Use the official category list for status, then describe the exact report separately.

Assuming a restart proves the cause

Note whether it helped, but keep the original steps and conditions in the report.

Treating a dated hotfix as a universal save repair

Check the named change and unresolved issue wording before retrying a route.

Changing save files without a backup

Back up first and follow only the current official instructions that apply to the observed problem.

FAQ

Adjacent questions

Where should I report a Mortal Shell II bug?

Use the Mortal Shell II Steam Bug Reports forum. The developer-authored known-issues thread points players there.

What should I try before reporting a PC issue?

Restart the game, verify game files, restart Steam, and avoid running as Administrator. These are first checks, not a promise of a fix.

Can I trade with the Collector or Night Merchant if the option is missing?

The developer currently lists being unable to trade with the Collector or Night Merchant as a known issue. Record your platform, version, location, and exact interaction state, then use the Steam Bug Reports forum; the thread does not publish a universal recovery fix.

Are all player-reported bugs confirmed known issues?

No. A report can be useful evidence, but it does not prove the cause, affected platforms, or a universal fix.

Did the October 13 hotfix fix every achievement or progression issue?

No. The dated hotfix names specific interaction, dungeon, and gameplay changes; it does not promise that every achievement, progression, or save problem is resolved.

Related guides

Continue from here

Browse all guides

Return to a current player task after recording the issue clearly.

Browse all guides