World
Bosses, navigation, healing and PC performance. Every field note identifies its evidence and version boundary.
What this section solves
The world volume treats exploration as a chain of recoverable decisions. Bosses ask you to recognize cues before forcing damage; interconnected routes ask you to name stable landmarks; healing asks you to preserve enough recovery for the objective; and PC performance asks you to reproduce a problem before applying fixes. These notes share one rule: verify the current build and keep a way back.
Prepare, observe, return
- Map the nearest anchor and return condition.
- Protect a healing reserve before optional exploration.
- Use a reconnaissance attempt to record two boss cues.
- If performance interferes, reproduce it in the same route and combat state.
- Return to Builds only when a specific combat decision needs a different tool.
Mortal Shell II Boss Guide
A phase-learning method for cues, posture breaks and healing windows.
Open archive →
Map & Fast Travel Guide
A landmark system for the compact world, beacons and safe return routes.
Open archive →
Healing & Items Guide
How to test consumables and create reliable healing windows.
Open archive →
PC Requirements & Performance
Verified PC requirements and a reversible performance diagnostic.
Open archive →Choose the right field note
Does the map guide promise early fast travel?
No. It explains how to navigate safely before any teleport is confirmed by the current interface. Travel unlock conditions are version-sensitive, so the guide uses beacons and unmistakable landmarks as dependable anchors.
Are all bosses listed?
No unsupported roster is presented as fact. The boss guide teaches reconnaissance, posture pressure, healing windows, and note-taking that apply to confirmed encounters; named pages should be added only when current evidence supports them.
How much healing should I carry?
There is no invented universal number. Keep a route reserve based on the next objective, stop optional exploration before that reserve disappears, and test unfamiliar consumables where failure does not ruin a boss attempt.
Where do performance fixes begin?
Begin with hardware, driver, resolution, preset, storage location, and one repeatable scene. Change a single setting at a time and compare frame-time behavior, then reverse changes that do not affect the problem.