Mortal Shell II Build Worksheet

What this worksheet is designed to prevent

Launch-week build advice often combines review access, beta information, one unusually strong interaction, and an undefined idea of "best." That can encourage players to spend scarce materials before they know whether a weapon's reach, recovery, and crowd control fit their Shell or their own timing. This worksheet does not calculate invented damage values. It creates a repeatable test so you can compare combinations in the retail version you are actually playing.

Enter the names exactly as they appear in the game and select one primary goal. A build cannot maximize survivability, posture pressure, range, control, and exploration convenience at the same time without tradeoffs. Choosing one goal makes the result measurable. Keep the same route and enemy group while testing alternatives; otherwise a harder region can make a better setup look worse.

A five-part build test

1. Survival baseline. Count the mistakes you can recover from and identify whether the Shell provides reliable mitigation, escape, control, or recovery.
2. Safe punish. Find the weapon attack that fits after a common enemy's recovery without forcing a trade. Note reach and your own recovery time.
3. Group answer. Test what happens when two enemies arrive together. Use terrain, a wider move, a sidearm, or a Shell ability and record which part prevents the second hit.
4. Posture conversion. Confirm how the setup creates a posture break and which follow-up can reliably exploit the opening.
5. Resource efficiency. Compare the practical improvement after one upgrade step before committing more. Preserve unfamiliar rare materials until renewability and respec rules are verified.

How to record a useful result

Write down the game version, platform, Shell, weapon, sidearm, relevant abilities, upgrade level, test route, and selected priority. Repeat the route at least three times. Record successful clears, healing used, deaths, and the first recurring failure. A single fast clear can be luck; repeated safe clears show that the combination is doing useful work.

If two builds perform similarly, prefer the one with clearer decisions and fewer rare requirements. A setup that depends on perfect parries, a narrow proc chance, or an item you cannot replenish may look stronger in a short clip than it feels over a complete dungeon. Conversely, a defensive Shell may appear slower while saving enough healing to create more meaningful boss attempts.

When to rebuild

Re-evaluate when a patch changes a Shell, weapon, Tarstone, enemy, posture, healing source, or upgrade cost; when the next region introduces a problem the current setup cannot answer; or when you discover that the planned priority no longer matches how you play. Do not rebuild solely because a tier-list thumbnail calls another option overpowered. Use the same worksheet and demand a repeatable improvement before spending again.

Example decision, without invented stats

Suppose one weapon reaches a target safely but recovers too slowly when a second enemy joins. The worksheet should not declare it bad or fabricate a damage-per-second value. Record that it succeeds in single-target punishes and fails the current group-control test. Then test whether the selected Shell or sidearm creates enough space to preserve its strength. If it does, the combination is coherent. If it does not, compare a faster or wider weapon on the same route before buying another upgrade.

The same method applies to survivability. A defensive ability has practical value when it consistently turns a lethal mistake into a recoverable one, not merely because its description sounds safe. Count healing used and completed attempts. Keep notes short enough to repeat after a patch. A build record is useful only when another test—or another player—can understand what was equipped, what was attempted, and why the result changed the next investment decision.