Sephiria all weapons: complete weapon index
A searchable index for Sephiria's six weapon families, their upgrade branches, and the evidence still needed for a complete current catalog.
What is confirmed
The official store page confirms six distinct weapons and more than fifty unique upgrades per weapon. The index should therefore start at the weapon-family level and expand into upgrade pages as each branch is captured in-game.
Fields for every weapon
Each entry should include the normal attack, dash, special attack, range, recovery, upgrade branches, and common artifact or tablet partners. Add unlock conditions only when a current run or official note supports them.
Use the Journal as the source of truth
The older Steam guide recommends the in-game Journal for reviewing unlocked artifacts, tablets, weapons, and upgrades. Use screenshots from that Journal to keep the index readable and version-specific.
The six-family index
The official store confirms six distinct weapons and a large upgrade tree for each. The index should therefore stay at family level until each branch has a current Journal capture.
For a quick comparison, show role, range, recovery, special-attack job, and the kind of artifact or tablet interaction that commonly completes the route.
Upgrade evidence standard
A weapon entry is ready when its name, unlock state, branch, and effect can be read in the current client. Add a gameplay clip only after the route has been reproduced outside the showcase run.
Keep historical early-access notes in a separate section so they remain useful without being mistaken for current balance data.
How to turn this index into a complete wiki
Each family should eventually split into a branch page and a named-upgrade page. The family page explains range, recovery, special action, and learning curve. The upgrade page records the exact text, source, version, and a screenshot from the current Journal. Readers can then move from a broad search to the evidence they need.
The launch notes are useful for spotting changes, but a release note is not a substitute for the live tooltip. Keep historical changes in the source block and reserve confident build claims for effects reproduced in the current client.
Weapon index: what is confirmed and what still needs a live capture
The official store confirms six distinct weapons. Use this sheet to keep permanent branch access separate from in-run upgrade discovery.
| Branch | Evidence in the public record | What a complete page still needs |
|---|---|---|
| Sword & Shield | One of the six official branches | Current Journal unlock screenshot and branch names. |
| Greatsword | One of the six official branches | Current Journal unlock screenshot and heavy-route tests. |
| Dagger | Launch notes record four new Dagger upgrades | Exact current upgrade labels and a repeatable close-range route. |
| Blade / Katana | Developer updates use both names across the timeline | A current client capture confirming name and unlock condition. |
| Crossbow | Developer updates describe it as a ranged weapon with reload behaviour | Current reload and upgrade screenshots after the 1.0 update. |
| Staff | Official updates connect Staff to Destiny Inscription progression | Current prerequisite and confirmation capture. |
Use this guide in a run
- 01Learn the base job
Test normal attack, dash, and special attack before judging the branch.
- 02Read the first fork
Record the upgrade that changes the weapon's job, range, or resource flow.
- 03Compare the danger room
Use the room where you usually lose as the deciding test, not a perfect showcase.
- 04Save the proof
Capture the current Journal name and a short run clip before publishing a tier claim.
Before you commit to this route
- Test normal attack, dash, and special attack separately
- Record safe range and recovery after each attack
- Capture the first branch that changes the weapon's job
- Link the current Journal or a gameplay proof