Skip to content
Mortal Shell II Completion Companion logo

Database · weapon

Mortal Shell 2 All Weapon Locations

Guide for all Weapon Locations in Mortal Shell 2. Find all Weapons for the Lord of War trophy & achievement in Mortal Shell II.

Mortal Shell 2 All Weapon Locations

August 17, 2026 by Gage Leave a Comment Mortal Shell 2 contains 8 obtainable melee weapons. Finding all weapons is required for the trophy/achievement Lord of War , along with one for obtaining each weapon individually. None of the Weapons are missable, you can find them all after the final boss in free-roam before choosing to enter New Game+. You can purchase maps from the merchant Merrick in Marrow Keep, which will mark the approximate location of each weapon on the overworld map. This is not required to find them though, so you can save your coin instead of purchasing the maps. Weapons are listed in the approximate order you will most likely unlock them by following normal game progression.

#1 – The Iconoclast

This is the first melee weapon you obtain, acquired at the start of the game during the Prologue.

#2 – Axe and Dagger

First, go south of Mushroom Village beacon to the area with the large burning pyre and the enemies nearby. On the north edge of the platform is an arch that when you walk through while facing the fire will cause a statue to appear. On the rope hanging from the statue is the Chapel Key. Then go northwest of Mushroom Village beacon, use the Chapel key to open the doorway and enter the Shrine of Trials dungeon. Progress to the end to find the weapon. In the first room walk backwards through the wall facing the statue, in the other rooms are basic push block floor switches, hit the blocks with your weapon to move them.

#3 – Veteran’s Battle Axe

Go northwest of Shattered Beacon dungeon, into a cave to find The King’s Crypt dungeon. Follow the main path through the dungeon until you drop down a long hole, the weapon is on a body right beside an enemy.

#4 – Great Martyr’s Blade

Go northwest of Gloomshade Grove Beacon, follow the paths to the northeast outside corner of the castle, where there is a hole in the wall leading to the Martyr’s Prison dungeon. You also end up at the well nearby if you take the back entrance from the Holding Cells Dungeon. Enter the dungeon and interact with the bag on the stone counter to move to a different area. Progress through the dungeon and defeat the 4 enemies in the locked room to access the room with the weapon.

#5 – Obsidian Hammer

From Outskirts of Mammon Beacon, follow the paths leading to the southwest of the area, where you can follow the wooden bridges towards the area full of wooden scaffolding, called Deserted Slums. In the center of the Deserted Slums, drop to the lower area with the enemies mining rocks. The entrance to the Obsidianite Mines Dungeon is on the southwest side of the pit area. Progress to the end of the dungeon and defeat the miniboss Prophet of Profane Infinities to automatically obtain the weapon.

#6 – Black Needle

Inside the Sester’s Gate Beacon. Progress to the end of the area and defeat the pair of bosses Twin Sesters and Stray Sesters to receive the weapon.

#7 – Axatana

Northeast of The Silent Steps Beacon, follow the path to the highest northeastern point where there is a Bone Gate that leads to the tower closer to the eastern Corrupt Gate. Press the button on the back of the tower to open the gate, and inside you can find the weapon behind an enemy.

#8 – Clockwork Scythe

Southeast of The Silent Steps Beacon, go to the large stone platform where you encounter the miniboss Sariel, the Endless. After you defeat him the first time, he will move through the walls to the south, opening them so that you can enter the Chamber of Becoming Dungeon. Follow him through the Dungeon and defeat him again. In the final room you need to attack the tombstones to break them to stop him reviving. Once you have done this with all 4 and fully defeated him, you will automatically obtain the weapon. That’s all of the Weapons in Mortal Shell II. More Mortal Shell 2 Guides: Shell Locations Tarstone Locations Beacon Locations Weapon Locations Sidearm Locations How to Summon Night (Increase Difficulty)

Evidence boundary for Mortal Shell 2 All Weapon Locations

Mortal Shell 2 All Weapon Locations is stored as a weapon claim from PowerPyx. The source snapshot was captured on 2026-08-18T08:19:46+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 powerpyx, 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 Mortal Shell 2 All Weapon Locations 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 weapon claim in the current build

Separate weapon identity, acquisition path, moveset observation, upgrade state, and comparison claim. A captured location can answer where to investigate without proving damage, scaling, tier position, or suitability for every Shell.

Treat Mortal Shell 2 All Weapon Locations 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 Mortal Shell 2 All Weapon Locations with the companion tools

Use the map for a matched acquisition lead and the tracker for confirmed ownership. Test reach, timing, and recovery in the current build before making a personal loadout decision.

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 Mortal Shell 2 All Weapon Locations 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 Mortal Shell 2 All Weapon Locations record

When the current build disagrees with PowerPyx, 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 Mortal Shell 2 All Weapon Locations.

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.