Sephiria Weapons

Weapons are the clearest expression of a Sephiria build. They determine the questions you ask of the inventory: how close you must stand, how long a target can remain alive, which damage pattern you want to reinforce, and whether a Tablet arrangement is worth protecting. A weapon guide should therefore explain a test, not just repeat a favorite build. If a recommendation has no chapter, upgrade context, or patch label, treat it as a lead rather than a fact.

How to compare weapons

Use the same short test for each candidate. Begin with movement and basic attacks, then watch how quickly you can respond after a dash or a missed strike. Next, inspect the first meaningful upgrade and note whether it changes damage, reach, defense, mobility, or a special interaction. Finally, play far enough to see whether the weapon still has a plan when rooms become crowded. A weapon that looks weak in a safe room may solve a later positioning problem; a weapon with impressive damage may fail because it cannot create space.

Keep the comparison variables visible. Write down the chapter, difficulty context, costume or persistent bonuses if applicable, Artifact support, Tablet arrangement, and the exact upgrade choice. Without those fields, “weapon A is better” often means only that one run had better rewards. A good page can recommend a starting experiment while admitting that balance and item pools may change.

Read the upgrade tree as a build map

The official store says each weapon has more than fifty unique upgrades. That is a large decision space, so the useful first question is not “which branch is strongest?” It is “which branch answers my current failure?” If targets survive too long, look for damage or uptime. If you cannot reach enemies safely, test range, movement, or crowd control. If the inventory is full of bonuses that do not activate, stop taking more of the same category and inspect the layout.

An upgrade should have a job and a follow-up. The job is the immediate improvement; the follow-up is the Artifact, Tablet, or room choice that makes the improvement reliable. When an upgrade has no follow-up, leave it tagged as a situational option. This approach also makes co-op comparisons fairer because teammates can explain why they chose a branch instead of arguing from an isolated damage number.

Where to go next

Open Weapons Guide for the roster and comparison fields, Weapon Upgrades for testing branches, and Weapon Unlocks for requirements once they are confirmed. Pair weapon research with the Artifacts and Tablets hubs. Those systems decide whether a weapon’s theoretical ceiling can be reached in the inventory you actually receive.

Learn one weapon before comparing six

The first comparison should answer whether the weapon’s basic action is understandable and repeatable. Use an uncomplicated room and observe the attack’s reach, recovery, and target priority. If the action is difficult to read, do not immediately label the weapon weak. Test whether a different movement rhythm or a safer distance makes the action reliable. This is especially important for new players, because unfamiliar timing can look like poor balance.

After the basic action is understood, add one upgrade question. Does the upgrade improve the same job, open a new range, or create a cost that the inventory must solve? Record the answer separately from a damage impression. A weapon that does less burst but creates a safer room can be the right learning choice, while a high-ceiling option may require more support than a first run can provide.

Keep a comparison card

For each test, record weapon, upgrade context, chapter or practice room, target type, solo or co-op mode, and version. Add a short result such as “keeps a retreat route” or “needs a teammate to finish setup.” This makes a future patch comparison possible without pretending that a single clear is a universal tier list. The Upgrades Guide and Unlocks Guide extend this card when current names are confirmed.

Pass the result to a build

A weapon observation becomes a build only when it has inventory support and a success condition. Carry the result to Builds, then test whether an Artifact or Tablet arrangement improves the action without removing the safety that made it useful. Keep solo and co-op records separate because shared enemy attention changes the value of reach and recovery.