How weapon upgrades work

Weapon upgrades appear through Anvil choices during a run. A selection changes the weapon’s direction, and later choices continue from the route already chosen rather than presenting every possible endpoint at once. The official scope promises more than 50 unique upgrades for each of the six base weapons, but it does not provide a public current English tree with every value.

Interactive upgrade explorer

Weapon enhancement paths

Choose a base weapon, follow a first enhancement, then inspect only its connected second enhancements. Every node keeps the image, name, and explanation from the same captured NamuWiki section.

139 nodes
2Maximum enhancements
1 + 2Second stage keeps the first
SeparateRequired Artifacts are not granted
Stage 1

First enhancement

9 choices
Stage 2

Second enhancement

Connected choices only

Select a first enhancement to reveal its connected second-stage options.

139 representative weapon images cover 48 first-stage and 91 second-stage sections. Extra images remain inside their matching detail view and are explicitly labeled as supporting references.

Community reference derived from NamuWiki, licensed CC BY-NC-SA 2.0 KR. Captured English labels are machine-translated and version-sensitive; the current in-game tooltip takes priority.

The captured Weapon Enhancement page adds two structural rules that matter when reading the tree. Each weapon can be reinforced up to two times, and the second-stage reinforcement accumulates the first-stage choice.

Treat the first meaningful choice as a route commitment. Read which part of the weapon it changes, identify the trigger or resource it expects, and check whether the current inventory supports that behavior. A famous final form is not useful if the earlier branch makes ordinary rooms less reliable or if the run never receives its required support.

Do Sephiria weapon upgrades grant Artifacts?

No. Some weapon groups have dedicated Artifacts that only enter the eligible pool while that weapon group is held, but choosing the related weapon upgrade does not add the Artifact to the inventory. If an enhancement depends on a named Artifact, confirm that the run already has it or check the Wishing Fountain before committing to the branch.

What this interactive explorer contains

The local research package contains 179 indexed image records from a saved community weapon-enhancement page. The current explorer maps 48 first-stage and 91 second-stage headings across Sword and Shield, Greatsword, Dagger, Crossbow, Katana, and Quarterstaff. Each selectable node uses the first representative weapon image from its own source section; later images from that same section remain in the detail view as clearly labeled Artifact or effect references.

The captured page was machine-translated, which produces awkward labels and unreliable proper nouns. The section number and image are more dependable for recognition than the English wording. Never copy a numeric effect or branch name from this archive without comparing it to the current client.

Read a branch before choosing it

First identify what the upgrade modifies: basic attack, Dash attack, special attack, guard, parry, reload, projectile, status effect, or resource behavior. Then identify the condition required to receive the benefit. Finally, decide whether that condition occurs often enough in the current build to justify continuing down the branch.

The same endpoint can perform differently when Artifact triggers, Tablet adjacency, Costume rules, and permanent unlocks change. Record those surrounding assumptions when sharing a route. A branch screenshot alone is not a complete build guide because it does not explain how consistently the upgrade activates or what inventory supported it.

The source page also separates a branch’s attack behavior from the stat window’s attribute damage. A normal attack cycle can contain multiple motions with different coefficients, so “attack damage” is not always one single hit. The archived coefficient tables are preserved as source material but are not repeated as current balance values here; use the live tooltip and stat window for a tested version.

Current families and historical entries

Sections 2 through 7 of the archive correspond to the six documented weapon families. Section 8 is titled as removed weapon enhancements in the captured source and is kept only as a historical reference. Removed entries should not be described as unlockable, current, or recommended unless the live game reintroduces them.

This distinction matters for search results because old images can remain indexed long after a patch. The source package retains the historical records, but the interactive selector excludes Section 8 so removed upgrades cannot be mistaken for current choices. If an Anvil does not show a branch in the current version, the current client wins.

Record an upgrade route accurately

When documenting a route, capture the game version, base weapon, each Anvil choice in order, the current tooltip, Costume, core Artifacts, Tablet relationships, and the type of evidence. Mark whether the result is a full clear, a partial run, a community recipe, or a retest. Those fields let another player distinguish a reproducible path from a final-screen screenshot.

Avoid converting translated names into confident new names. If the English client spelling cannot be verified, describe the image by family and branch position instead. Exact damage, duration, cooldown, cost, and probability values should come from the live tooltip for the tested version.

Practical branch priorities

An early upgrade should make the weapon more consistent, safer to use, or better able to reach enemies. Later choices can raise the ceiling after the route already clears ordinary rooms. If a specialization amplifies a trigger that rarely occurs, it is weaker in practice than a modest branch that supports every encounter.

Keep a fallback before pursuing an endpoint. Crossbow still needs a safe firing and reload loop if Minigun never appears; Dagger still needs a way to enter and leave range if Frozen Smelt is absent. A route is robust when its earlier stages remain coherent rather than existing only to unlock the final name.