Database · sidearm
Best Sidearms Tier List | Mortal Shell 2
This is a tier list of the best Sidearms in Mortal Shell II. Learn more about the best Sidearms, their rating, and strengths with this guide!
Evidence boundary for Best Sidearms Tier List | Mortal Shell 2
Best Sidearms Tier List | Mortal Shell 2 is stored as a sidearm claim from Game8. The source snapshot was captured on 2026-08-18T08:18:32+00:00 and last checked on 2026-08-18; its dataset label is Launch 1.0. Read the summary at the top as the captured conclusion, not as independent gameplay testing by this companion. The single source evidence label describes how many source layers support the record, while needs recheck describes whether its version still needs review. Neither label silently upgrades an unverified detail into current fact.
Keep the record attached to its attributed source URL, source identifier game8, platform scope, and review date. The page may help define a question or route lead even when the normalized source body did not pass the publishing gate. In that case, the missing body must remain missing: do not expand Best Sidearms Tier List | Mortal Shell 2 with locations, rewards, statistics, steps, or compatibility claims inferred from the title. A short source conclusion plus a precise verification plan is safer than fabricated completeness.
Verify the sidearm claim in the current build
Verify the sidearm identity, acquisition route, inventory state, interaction, and any performance statement independently. A location conclusion is not evidence for damage, upgrade efficiency, or a universal ranking unless the captured source explicitly establishes those claims.
Treat Best Sidearms Tier List | Mortal Shell 2 as a comparison claim that needs criteria, alternatives, version, and evidence for every ranking dimension. Preserve the captured recommendation, but do not manufacture scores when the source model lacks them. A player may record a preferred option after a reversible test without presenting personal comfort as an objective best-in-game result.
Before acting, record the application branch and platform actually launched, then compare them with the stored platform list and Launch 1.0 label. Use the smallest test that can confirm the page's central question without spending scarce resources or crossing an irreversible route point. Note the starting state, action, expected result, and observed result. If any one of those is unknown, keep that part unresolved instead of converting absence of evidence into a negative answer.
Use Best Sidearms Tier List | Mortal Shell 2 with the companion tools
Use the map to investigate the named acquisition lead and the tracker to record confirmed ownership. Test the current interaction before accepting a build recommendation that depends on the sidearm.
Search results, map favorites, route checks, and tracker completion all belong to this local companion profile. They do not query the game's inventory, quest flags, platform achievements, cloud save, or storefront entitlements. Mark only the exact Best Sidearms Tier List | Mortal Shell 2 decision or supported target that the game confirmed. A related result can remain a useful lead without being checked, and an exported JSON profile preserves companion state only; gameplay recovery requires the platform's separate save system.
Reconcile and close the Best Sidearms Tier List | Mortal Shell 2 record
When the current build disagrees with Game8, preserve both observations. Record the dated source claim, the release build tested, the exact mismatch, and whether the difference affects only a route step or the central conclusion. Look for a current official or independently attributed source before changing the record. A similar noun in patch notes is not enough; the update must address the same subject, condition, and result represented by Best Sidearms Tier List | Mortal Shell 2.
Close the review with a compact receipt: question tested, source and date checked, platform and build used, action performed, observation made, and local target changed. Keep unknown, skipped, failed, and completed states separate. If the page remains marked needs recheck, retain that warning even after one successful personal test; one run can confirm a local outcome without proving universal behavior. This receipt makes later updates auditable and prevents stale guidance from being silently presented as release-wide fact.