Database · npc
List of All Cosmetics | Mortal Shell 2
Cosmetics change the appearance of your character in Mortal Shell 2. Check out the list of all available cosmetics in the game, the different types of cosmetics, as well as what cosmetics are in this guide!
Evidence boundary for List of All Cosmetics | Mortal Shell 2
List of All Cosmetics | Mortal Shell 2 is stored as a NPC or character claim from Game8. The source snapshot was captured on 2026-08-18T08:18:22+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 List of All Cosmetics | 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 NPC or character claim in the current build
Separate character identity, location, dialogue state, quest involvement, reward, and any lockout. A character list does not establish a complete questline, while a location claim from one build does not prove the same appearance conditions in another.
Treat List of All Cosmetics | Mortal Shell 2 as a completeness claim rather than a loose collection of examples. Define the source snapshot, count the named entries it actually supplies, check for duplicates, and label unknown release additions. Do not call the list complete merely because every imported row has a local check; source coverage and player completion are different questions.
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 List of All Cosmetics | Mortal Shell 2 with the companion tools
Use the map for a named meeting-point lead and search for an attributed quest record. Keep the tracker open until the relevant interaction or reward is confirmed in the game.
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 List of All Cosmetics | 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 List of All Cosmetics | 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 List of All Cosmetics | 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.