Sephiria Weapon Upgrades Guide: Choose a Branch You Can Actually Play

Why a static upgrade chart can become wrong

TEAM HORAY's full-release announcement says Sephiria added more weapon upgrades. Its later updates also continue to fix and change combat systems. That means an old chart can still help you recognise a branch name, but it cannot safely settle the live effect, a number, or the best follow-up for the version you are playing.

A public player-maintained Compendium organizes upgrade branches for all six weapons across multiple tiers. That is useful for seeing that a weapon can develop in different directions. It is not an official balance document, and it should not be treated as proof that every entry, value, or interaction is unchanged on your save. The current in-game branch description is the decision-making source for a real run.

A four-step weapon-upgrade choice

Use one small loop whenever you see a branch you have not taken before. It prevents the common mistake of choosing a label first and only discovering afterwards that the action, range, timing, or resource requirement does not suit the way you play.

The point is not to prove that a branch is weak or strong after one room. The point is to make a specific observation that you can reproduce, then let the rest of the run support that observed action.

• 1. Start with the weapon action you already use reliably, such as its ordinary attack, guard, charge, reload, or stance change.
• 2. Read the live branch text and name the one thing it changes: an action, a damage type, a trigger, or a resource rule.
• 3. Test one branch in Training Grounds or in a low-risk situation before planning the rest of the board around it.
• 4. Carry only an observed conclusion into the run, such as ‘this makes my reload rhythm easier’ or ‘this costs more attention than I can spare.’

Read the effect before you read the number

A branch that changes how you attack can matter more than a branch whose number merely looks larger. First check whether the description changes a normal action, special action, guard, dash, projectile, status effect, or resource use. Then ask whether you can actually create the stated trigger during the rooms you are facing.

This is especially important when an effect asks for a condition. A reward for a guard, a repeated hit, a reload cycle, a damage type, or a stored resource has value only if your current weapon rhythm creates that condition often enough. If you cannot state the trigger in plain language, do not reserve your next Artifact or Tablet space for it yet.

Test the branch before rebuilding the whole run

TEAM HORAY added Comprehensive Training Grounds so unlocked weapons and items can be tested without asking a live tower run to answer every question. Take a branch there with one narrow question: what button or condition activates it, what does it replace or add, and what do you need to watch while using it? Repeat that same check before comparing another branch.

After the test, change only one supporting piece at a time. If the branch needs a damage type, resource, or particular action, try one relevant Artifact or Tablet and check whether the action became clearer or merely more complicated. This gives you an honest build direction without pretending that the first community table you found has already solved the run.

When sources disagree, keep the live text

Treat source quality in order. The live in-game description decides the immediate choice; TEAM HORAY's official patch notes explain confirmed additions and corrections; the community Compendium helps you find branches worth checking. A screenshot, a video, or an old copied list comes after those sources, not before them.

If a branch is missing, renamed, or described differently from a community table, do not force it to match. Record the version and the current wording, test the behavior once, and leave the uncertain detail out of your plan. That is slower than copying a tier list for five minutes, but it keeps a real guide useful after the next balance update.