01

What counts as a weapon upgrade?

A base weapon branch, a named Journal upgrade, and a run-only artifact are different things. This guide keeps them separate so a strong run does not look like a permanent unlock.

Before copying an upgrade path, write down the weapon family, the exact Journal wording, the current version, and whether the choice changed the attack, movement, range, or resource cost.

02

Choose the first upgrade by job

Pick the job your run needs first: safer entry, more room control, better range, faster recovery, or a stronger boss punish. A larger damage number is not always the best first choice if the route keeps ending in the same dangerous room.

Test the first branch in one normal room, one crowded room, and one boss window. Keep the branch that solves the problem you actually have, then build artifacts and tablets around it.

03

Family-by-family checks

For Sword and Shield, check block recovery and how the branch turns a safe defense into damage. For Katana and Dagger, check entry and exit timing. For Crossbow, check firing lanes and reload safety. For Staff, check spell or grimoire cost and room control.

Greatsword needs a clear commitment window and a safe recovery plan. Whichever family you use, record the first upgrade that changes its job instead of ranking every upgrade with one global score.

04

Sword and Shield upgrades

Sword and Shield upgrades are easiest to compare by what happens after a block or parry. Check whether the branch gives you a safer recovery, a clearer counter window, or more control when several enemies close in.

For a current entry, record the exact Journal name, the first branch choice, the material or cost shown in your client, and the room where the upgrade actually helped. Do not call a branch best until it has survived both a crowded room and a boss window.

05

Staff upgrades

Staff upgrades should be judged by the spell or grimoire loop they improve. Check resource cost, cast recovery, range, and whether the upgrade still leaves you a way to control a crowded room.

Keep Staff upgrade notes separate from a general magic build. A build explains the full loadout; this page records the branch, prerequisite, current tooltip, and the simplest test that proves the upgrade is useful.

06

Anvil upgrades: verify the system first

Players search for Anvil upgrades, but the exact function and wording should be confirmed in the current client before a dedicated page is created. Open the Anvil, capture its menu, and record whether it changes a weapon, unlocks a branch, or only affects the current run.

Until that check is complete, keep Anvil notes here as a verification task rather than publishing a made-up material list or upgrade order.

07

Where to verify materials and unlocks

Use the current in-game Journal for exact upgrade names, materials, costs, and prerequisites. Older community notes can show where to look, but they should not be treated as current values without a fresh capture.

If a material or unlock condition is not visible in the current client, leave it marked as pending. A short verified entry is more useful than a detailed table filled with old numbers.

08

A simple upgrade order

First take the branch that keeps your main action safe and repeatable. Next add the upgrade that fixes the room where you usually lose. Only then chase a late damage option or a rare synergy.

Write the order as three short lines—first branch, room fix, boss option—so a reader can use it during a run without reading a full build essay.

09

Do not mix permanent and run-only progress

The weapon family and Journal unlock are account or route information. Artifacts, tablets, and temporary stat boosts belong to the current run. Put them in separate columns whenever you record a path.

This distinction also makes updates easier: a patch may change a run interaction without changing the base weapon or its unlock route.