Mortal Shell 2: How to Get Tar Golem Achievement Without the Autosave Trap

To get the Tar Golem achievement in Mortal Shell 2, you need to reduce Tar Golem to 0 HP yourself. The normal story defeat sequence does not appear to count for the unlock. Current public footage and reporting also suggest that once the scripted post-fight sequence finishes, the game can autosave a state that is bad for clean retries, so the safe approach is to treat every attempt like a one-shot run from a protected pre-fight save.

The short version is this: keep a save from before the encounter, go all-in on actually emptying the boss health bar, and if the achievement does not appear before the cutscene/reward flow fully settles, quit out before that sequence locks in a new autosave. If the cutscene autosave has already overwritten your only usable file, the best current evidence says you may need to load an earlier save or start a fresh one.

What the Tar Golem achievement is actually checking

The important detail is that the achievement trigger appears to be tied to Tar Golem hitting 0 health, not to “finishing” the encounter in the way the story first presents it. Public capture of the unlock shows the achievement text as “Finish the Fight”, and the same footage indicates that the game still forces the usual wipe and replayable cutscene flow afterward. In other words, the achievement seems to care about the boss HP check, while the game narrative still behaves as if you were meant to lose there.

That is why so many players get tripped up. You can do the encounter “correctly” for story purposes and still miss the achievement. You can also earn the achievement and then see what looks like the same outcome you always get, which makes it feel as if nothing happened. That part is apparently normal. Do not expect a special victory room, a new checkpoint state, or a clean post-boss transition just because the platform says the achievement unlocked.

Protect a clean pre-fight state before you try it

The whole workaround lives or dies on save discipline. If your current file is already parked after the cutscene/autosave, you may not have much room to recover. If you still have a save from before the Tar Golem sequence, preserve it before you do anything else. If the game gives you multiple manual slots, use two, not one. If your platform allows an official backup method, this is exactly the kind of boss sequence where it helps.

What you want is a point you can return to without relying on the encounter’s own cleanup logic. Do not assume the game will hand you a convenient retry state after the scripted scene. Current evidence points the other way: once that sequence finishes, the autosave can effectively overwrite the clean setup you wanted.

• Keep one save from before the Tar Golem trigger.
• If possible, duplicate that save into a second slot before attempting the fight.
• Avoid experimenting on your only progression file if you care about preserving a clean retry.
• If you already triggered the post-fight scene on your main file, stop and check for an older backup before doing more attempts.

The safest attempt workflow for the achievement

Start from the protected save, not from faith in the checkpoint

Load the save you specifically preserved for this. The goal is not merely to survive long enough to see the story move forward. The goal is to push Tar Golem all the way to zero. That changes how you should think about the fight. If you have been playing it like a scripted loss where conserving healing is the main priority, switch mindset. Damage output matters more here than “cleanly losing” in the intended way.

Build for reliable damage windows

Because the check appears to happen at 0 HP, this is one of those encounters where a safer but lower-damage approach can still fail the achievement even if it feels stable. Use your strongest upgraded gear, your best damage consumables, and any loadout that turns short punish windows into real progress. If you have to choose between a defensive setup that drags the fight out and a burst setup you can control, the burst setup is usually the better fit for this specific goal.

You do not need to play recklessly, but you do need to play with intent. If there is a moment where you normally back off because the story seems to be steering toward a scripted outcome, do not. Treat the health bar as the real objective. The achievement logic, based on what is currently public, appears to agree with that.

Watch for the achievement at the HP-zero moment

The unlock should be associated with the boss actually reaching zero health, not with the later cutscene completing. That means you should not sit through the whole sequence hoping the game awards it at the end. If the health bar is gone and the achievement appears, you are done. At that point, the fact that the game still wipes you or replays the same broader flow is not a problem unless you were also trying to preserve a special sandbox state on that file.

If the boss drops, the scene starts, and you do not get the achievement, assume the attempt failed for achievement purposes. Waiting to see whether the game sorts itself out later is the mistake that tends to turn a recoverable miss into a bad autosave.

When to quit so the cutscene autosave does not burn the attempt

The conservative rule is simple: once it is clear the achievement did not trigger, do not let the post-fight sequence finish if you still need a clean retry state. Exit as early as your version safely allows. If there is an in-game Quit to Title option available before the save writes, that is cleaner than a hard close. Force-closing the application should be treated as a last resort because abrupt shutdowns can create different save issues.

The exact autosave moment is not fully mapped in public evidence, so the safest assumption is that the danger window is the entire scripted aftermath. Do not rely on “maybe it saves later.” If you are trying to protect the pre-fight state, the right habit is to quit the moment you know the run did not produce the achievement, not after the scene settles and control returns.

This is also why the one-shot framing matters. Go in expecting that every failed attempt needs an immediate reset. That mindset keeps you from making the classic error of watching the cutscene out of curiosity, only to discover that curiosity cost you the only clean file you had.

If the cutscene autosave already happened, reset this way

If you already let the scripted sequence complete and the game saved afterward, the recovery options get much narrower. Based on current public reporting, there is no clearly verified method to create a useful manual save during or immediately after that sequence and still preserve an achievement-ready state. Confidence is low on any workaround beyond rolling back to an earlier save.

In practical terms, your reset order should be:

• Best case: load an earlier manual save from before the Tar Golem encounter.
• Also workable: restore a backup copy of your save if your platform supports that.
• Worst case: if your only file is the overwritten post-cutscene autosave, assume you may need a new save file for another clean attempt.

That answer is not satisfying, but it matches the evidence available right now. The encounter appears to decouple the achievement from the normal story resolution, and the autosave behavior appears to punish anyone who assumes the game will preserve a pre-boss retry point for them. If you are already past the safe rollback window, spending an hour hunting for a magical in-place fix is usually less efficient than confirming whether you still have an older save somewhere.

Common mistakes that waste the most time

• Assuming the first defeat cutscene counts. It apparently does not. The boss needs to hit 0 HP.
• Letting the full sequence play out after a failed attempt. That is the easiest way to lose your clean retry state.
• Using only one save slot. A single slot turns a quirky achievement into a file-management problem.
• Playing too cautiously. The achievement is tied to damage completion, so low-pressure chip play can be the wrong approach.
• Expecting a special post-win state. Current evidence says nothing meaningful changes in-game after the unlock; the game can still wipe and proceed as usual.

The last point is especially important. Players often think they failed because the scene looked unchanged after the unlock. That does not necessarily mean anything went wrong. If the achievement popped, the game does not seem obligated to reward you with a visibly different outcome.

What is still uncertain right now

The main uncertainty is how much of this behavior is final and how much is specific to the current build. Public guidance has already flagged the possibility that the Tar Golem achievement behavior is beta-specific. That matters because a later patch could change the trigger, the post-fight sequence, the autosave timing, or all three. If the game updates, treat older advice as suspect until players confirm the behavior again.

The second uncertainty is exact save timing. There is strong enough evidence to say the cutscene/autosave sequence is dangerous for retries, but not enough to promise a universal “safe frame” for every platform or build. That is why the guide above stays conservative: preserve a pre-fight save, aim for HP zero, and exit early if the achievement does not appear. It is the lowest-risk workflow even if small technical details vary.

Practical takeaway

The Tar Golem achievement is less about winning the story encounter and more about forcing a hidden HP-zero check before the game drags you back into its scripted aftermath. Protect a save before the fight, commit to full boss damage instead of the expected defeat flow, and do not let a failed attempt ride into the cutscene autosave. If that autosave already happened, stop looking for a clean in-run fix first and look for an earlier save, because that is the most reliable reset path supported by current evidence.