Urgent.News

What's breaking now, across thousands of outlets.

Tech

How to complete Four Fierce Axes in Phantom Blade Zero

How to complete Four Fierce Axes in Phantom Blade Zero

The Four Fierce Axes quest in Phantom Blade Zero can be completed by following a series of steps after discovering the quest through a Four Axes case file in Broken Puppet Valley. Initially, you must uncover the truth behind the Four Axes Rebellion by reaching an outpost and defeating Peng Meng, the boss there. Following this, gather evidence of the conspiracy against the Four Axes by locating seven additional Four Axes case files scattered throughout Weeping Creek Valley.

These files are hidden in various locations, such as near the Broken Puppet Valley bell, on a corpse by a shrine, before the Outpost Courtyard bell, near the Axemaster's Holding Cell bell, after obtaining the Sha Chi Tower Base Camp Key from Sha-Chi Tower, and after progressing through the Festering Secret quest to receive it from the Lieutenant.

The 7th case file becomes accessible once you reach the Village of Lu region after the Crimson Forest, where you must complete the Leave None Alive quest, battle enemies, and finally deliver all the gathered evidence to the Child of Insight in Pangzhen, the 4th region of the game. Completing this quest yields the reward, the Blood Oath Dagger, which permanently Tempers the Dread Axe.

Written by urgent.news from PC Gamer's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at pcgamer.com →

More in Tech

A preflight for on-chain swaps: four rehearsals, three refusals, zero transactions

Many swaps that fail on-chain, and burn gas doing it, would have shown the same failure in a free eth_call first. Here is a ~30-line preflight for swaps built with the BlazePhoenix SDK, run through…

  • Pre-flight check prevents on-chain swap failures with zero gas cost
  • BlazePhoenix SDK simulates swap transactions to reveal issues
  • State override enables rehearsal of swaps without gas expenditure

KMP Architecture: Share the Contract, Keep the Platform Details

The first difficult Kotlin Multiplatform decision is often not how much code to share. It is where platform behavior should enter the shared code. Take an article reader that opens an external link.

  • Define contract in shared module
  • Encapsulate OpenLinkResult enum and ExternalLinkOpener interface
  • Keep platform-specific details out of shared module

More from Thursday 29 October →