Skip to content
Mortal Shell II Completion Companion logo

Trophy record

Bag Holder Trophy & Achievement Guide

You’ve mastered nothing and this is your reward. Pretty pointless, eh?

Requirement

You’ve mastered nothing and this is your reward. Pretty pointless, eh?

Captured guidance

This trophy is awarded for completing the interaction chain with the character Baghead, which triggers a joke ending for the game. They can be found southwest of Gloomshade Grove Beacon, through the Bone Gates that lead to an area called Desolate Peak. Speak with them a couple of times, and they will prompt you to sit on the ground nearby with the other NPCs. After sitting down once, speak with them again and continue responding Yes to their questions, and they will ask you to bring them something. There are items you can pick up around the area, but you don’t want to give them any of them. Sit down once more, then after sitting speak with them again and continue answering Yes to trigger the joke ending scene. You can skip the credits if you want, then reload your save to be back at the nearby Beacon.

This record reproduces a captured source conclusion with attribution. It is not claimed as independently verified gameplay.

Requirement boundary for Bag Holder

Bag Holder has the captured requirement “You’ve mastered nothing and this is your reward. Pretty pointless, eh?.” Treat that wording as the exact completion question. The supporting summary may explain the cited route, but the title, icon, rarity, and neighboring trophies do not add hidden conditions. This companion attributes the record to the linked PowerPyx roadmap and last checked it on 2026-08-18. It does not claim an independent unlock test, inspect the platform account, or infer a missing step from the trophy name.

Break the requirement into a start state, player action, in-game result, and platform unlock. Write down which part the captured source establishes and which part still needs a current-build observation. If the requirement names several objects, encounters, or actions, verify each one instead of checking the whole target after the first match. If the wording is broad, keep the scope bounded to the cited roadmap rather than inventing a count, location, or sequence that the record does not supply.

Prepare the Bag Holder attempt

Bag Holder is not flagged as missable in the captured roadmap, but that label does not guarantee immediate access, automatic platform synchronization, or identical behavior in every patch. Plan the smallest attempt that satisfies the named requirement, retain ordinary platform save precautions, and keep the local target open until the game and platform provide the expected confirmation.

Open the attributed source before the relevant route point and compare its checked date with the game build being played. Confirm that the correct application, save slot, platform profile, and network state are in use. Clear unrelated experiments from the attempt: perform the smallest sequence that can satisfy You’ve mastered nothing and this is your reward. Pretty pointless, eh?, then wait for the in-game and platform feedback. A nearby collectible, boss victory, or route transition is not proof unless it is the named condition.

Verify the unlock without guessing

Record the starting checkpoint, action performed, immediate game response, platform notification, and trophy-list state. If the notification is delayed, refresh the platform list through normal platform controls and preserve the time of the attempt. Do not repeat an irreversible action merely because a pop-up was absent, and do not mark Bag Holder complete from memory. The platform trophy state is the unlock evidence; the game's local state can support diagnosis but is not a substitute for it.

If the requirement appears satisfied but the unlock is missing, check the known-issues record for a symptom that names the same target and version. Capture the shortest reproducible sequence before restoring a save or replaying the action. One failed attempt can justify keeping the target open and documenting a mismatch; it cannot prove that Bag Holder is broken for every player or that the attributed requirement is universally wrong.

Manage the local Bag Holder state

The progress button stores one local companion target for Bag Holder. Set it complete only after the platform unlock is confirmed. Unknown means the condition has not been verified; skipped means a route decision intentionally deferred it; failed means an observed attempt did not produce the expected result. Keep those states distinct so the roadmap percentage remains an honest summary. Exported progress can restore this local choice, but it cannot award a trophy or modify the game save.

Close the record with the source URL, 2026-08-18 review date, game build, platform, save slot identifier that contains no private credential, action, observation, and final target state. If a patch or new source changes the requirement, preserve the older receipt and reopen only the affected question. One successful run confirms the local outcome; broader wording should remain attributed until independently cross-checked.