Database · 12 records
Weapons
The cards carry decisions and evidence, not invented stats. Captured launch material remains marked for recheck until it passes the release review queue.
Use weapon records as acquisition evidence
The weapon index organizes captured acquisition pages, route references, and source status in one list. It does not convert isolated guide conclusions into a universal best-weapon table. Start with the record that matches the weapon named by your route or build, review its evidence label, and follow the attributed source when the current page is marked for recheck. A source-backed location can support where to investigate while still leaving moveset, damage, and upgrade efficiency unclaimed when the dataset does not establish them.
Mark a weapon target complete only after confirming it in the game. The map and tracker can share the target's local state, but neither tool reads inventory data. If a marker, source page, and current release disagree, keep the target open and use the discrepancy as a review task. This preserves a practical acquisition checklist without disguising a captured launch snapshot as independent testing.
How to use the Weapons index
This index contains 12 Weapons records. It organizes source captures so a player can find a named question, inspect its evidence label, and decide what to verify next. Examples in the current set include Best Weapon Tier List | Mortal Shell 2; How to Get Axatana | Mortal Shell 2; How to Get Axe and Dagger | Mortal Shell 2. A card is an attributed lead, not proof that its conclusion, location, value, or route still matches the release build. Open the dedicated page before acting, then keep the title, summary, source, version, and review date together as one evidence record.
The current Weapons set cites Game8, PowerPyx, MortalShell2.org. Source names describe provenance, not automatic authority, and multiple pages from one publisher do not become independent corroboration merely because their URLs differ. 12 records carry a needs-recheck version state. Use that label to prioritize current-build review; never remove it because a card looks complete or because another page repeats the same captured conclusion.
Find the right Weapons record
Start with the exact decision blocking the run: identify an object, reach a place, answer a platform question, prepare a route transition, or reconcile a changed build. Search for that subject and compare the returned hub, type, source, and date. Open one primary record instead of reading every card as a combined guide. If two pages answer different questions, keep both; if they make the same claim from the same source family, do not count them as independent confirmation.
Read list, location, how-to, ranking, and yes-or-no titles according to their intent. A list needs a defined snapshot before it can claim completeness. A location needs a current route confirmation. A how-to needs a start state and observable stop condition. A ranking needs criteria and alternatives. A time-sensitive answer needs the same platform, edition, branch, and date. These checks prevent the Weapons index from turning titles into facts the captured body never supplied.
Move from Weapons evidence to local progress
Use the map only for a matched spatial lead, the roadmap only for an ordered route decision, and the tracker only for a supported local target. None of those tools reads the game save, inventory, quest flags, achievements, or storefront entitlements. Confirm the named result in the game before checking it. An imported marker, search result, or completed card can help organize work without becoming evidence that the underlying objective is finished.
When a record disagrees with the current release, retain the attributed source and capture date, record the application build and platform tested, and describe the exact mismatch. Seek a current official or independent source that addresses the same condition and result before editing the conclusion. Close the review with a receipt containing the question, evidence, test, observation, and local state change. This keeps the Weapons index useful without hiding unknowns or manufacturing release facts.
Before leaving the Weapons index, compare the open work with all 12 visible records and remove only true duplicates from the review queue. Keep two similarly named pages when their intents, platforms, versions, or source conditions differ. Record why a page was selected, deferred, or rejected so another session can resume the same evidence question without rereading every card or mistaking an unreviewed record for a negative result.