Steam scope: Windows PC.
The Mortal Shell II Steam listing separates supported language information into different categories. That matters because interface text, subtitles, and full audio are not the same promise. This guide shows how to verify the language a player needs and how to test a setting without losing the original configuration. It does not invent a menu path that the pre-release product page has not published.
Read the language table
Find the row for your language and check each column independently. If the page marks interface and subtitles but not full audio, explain exactly that boundary. Do not translate “supported” into “voiced.” A guide should also record the page date because store language tables can change before launch.
When the game opens, compare the store claim with the in-game language selector. Record the label, whether the change requires a restart, and whether menus, subtitles, and audio actually change. If the selector is missing or the result differs, save a screenshot and report the product AppID before assuming a bug.
Change one setting
Start from the default. Change one option and observe a known scene. This is useful for camera, input prompts, subtitle size, brightness, audio mix, and any accessibility control the released game provides. If several settings change at once, a player cannot tell which one solved the problem.
Keep the original value in your note. A reversible guide tells the reader both where the option lives and how to undo it. If the option affects performance, move to the Technical hub for a repeatable test rather than claiming that a preset is best for every Windows machine.
Interface and subtitles
Readable text is a practical combat feature. Test the size, contrast, and background against a dark environment and a bright effect. If a language change alters line length or breaks a prompt, note the exact screen and version. Do not use a translation screenshot from the Open Beta to promise the same layout in the base game.
For multilingual article links, preserve the player’s locale. A Spanish, Japanese, or Brazilian Portuguese reader should be able to switch from the settings article to the same locale’s combat or technical page. The language switcher is shared site behavior and should not be replaced by manually copied English links.
Audio checks
Listen for dialogue, combat cues, and menu feedback separately. The Steam language table is not enough to state that all three have full voice support. If an audio setting changes a mix rather than a language, describe the player-visible result and leave unsupported categories clearly marked.
Beta and base-game boundary
The Open Beta AppID is 4711740 and the base game AppID is 2584270. A Beta menu can provide a useful clue, but the full product may change labels or available options. Record the product before reproducing a setting issue and do not file a base-game bug report with Beta-only assumptions.
If a setting appears to reset, test a normal exit and a fresh launch before changing files. Check whether the game has a separate apply button, whether Steam Cloud has finished syncing, and whether the player changed the language in Steam or inside the game. These checks describe a reversible investigation; they are not proof that the release build uses one particular save architecture.
Also note whether the selector changes immediately or only after restarting. That small detail helps a player avoid judging a translation or subtitle option before it has taken effect.
FAQ
Does a supported interface language guarantee voice acting?
No. Check interface, subtitles, and full audio separately.
What is the safest way to test settings?
Record the default, change one option, test a known scene, and keep a reversible path back.
Why mention the AppID in a settings report?
Because the Open Beta and base game are separate products and may expose different menus.
Sources: the Mortal Shell II Steam language table and the separate Open Beta listing. Checked 2026-08-09.