Build lab · Evidence before tier lists

Sephiria Builds for the Current Version

Choose a weapon route, assemble its core interaction, and adapt the remaining inventory to your drops. Start with the practical guides below, then explore the research routes.

9 active research routes

Start with a working interaction

Choose the next piece your run needs

Evidence boundary

Research routes are not completed builds

A source-backed record proves that the item and its documented change exist. It does not prove that every listed record interacts, is required, or is best. Separate test candidates are shown only where a relationship still needs an in-game check.

Research routes

9

Community tested

0

A research framework is a route worth testing, not a finished loadout. Send reproducible run notes and screenshots to [email protected].

Evidence lab · local draft

Turn one real run into a reviewable field report.

Good Build pages are reproducible. Capture the context that makes a run succeed, then export a report for your own notes or an editorial evidence review.

Publication boundary

A draft is not automatically a tested Build, recommendation or ranking.

01 · Run identity
02 · Context and setup
03 · Outcome and proof

Choose a build around the action you can already use

Start with your equipped weapon and the pieces in your active inventory. For a Lightning Blade route, establish Arges and Storm Cloud before spending more space on damage support. For an evolving Artifact, match its trigger to your weapon: Perfect Guard for Faded Shield Crest, Sheath or Unsheath for Rusty Tsuba, and Reload for Stiff Crank. Open the guides above for the exact conditions and current patch values.

Then check the resource that lets the interaction work. Cloud Slash needs 5 MP to spend its stacks; a reload build needs time to complete the reload and use its following attack window. If the action cannot be used reliably, solve that problem before selecting another peak-damage item. Keep defense that helps you reach the next opening, and compare optional pieces only after the core action is working.

Adapt the board to the drops you get

Separate core pieces from support. If Arges or Storm Cloud is missing, continue with a usable Blade route until the pair is available. If only a preferred support item is missing, keep the interaction and fill the space with resource or survival help you can use now. Save an inventory sketch in the Planner when comparing alternatives, then check the actual effects in your in-game tooltip.

The detailed guides above cite the official mechanics and explain these decisions. The nine research cards below them remain frameworks for further testing, with their current status visible on each card. Use the guides for assembly and troubleshooting; use a research card when you want to record and compare a run’s weapon, board, version and outcome.

Build questions, answered

How to use these research routes

These short answers separate versioned source records from run advice and claims that still need a current in-game check.

What do Research framework, Needs review and Community tested mean?

Research framework is a useful direction with documented anchors, not a finished loadout. Needs review marks a term or interaction that still needs a current in-game check. Community tested requires repeatable run records with the weapon, version, difficulty, board and outcome.

Is there one best Sephiria build?

No. A route changes with the weapon, difficulty, drop sequence, Solo or Co-op context and the actions a player can execute consistently. Start with a weapon rhythm you can use reliably, then choose offered effects that reinforce that plan instead of forcing a screenshot-perfect loadout.

Why are source-backed starting records and research candidates separate?

A first-party record can confirm that an item or documented change exists, but it cannot prove that every listed piece is required or interacts with the others. Candidates stay separate until a current in-game test confirms the relationship, so readers can distinguish evidence from a lead worth testing.

Which build route should I try for my weapon?

Choose the route whose decision matches the weapon and effects actually offered in the run. Read its patch-review boundary and source records first, then use its candidates as optional test ideas. Do not restart solely because an anchor fails to appear; these pages describe directions, not fixed drop orders.

What evidence can move a route to Community tested?

Record repeatable runs with the weapon route, game version, difficulty or active modifiers, inventory board and outcome. Screenshots or retained video make a result easier to review. One successful run can be useful evidence, but it does not establish a dependable route on its own.

Why does this page not list exact damage, drop rates or Tablet geometry?

Official patches can change values and effect wording. Until a current-version source or reproducible in-game check supports a number, range or placement rule, Sephiria Wiki leaves it unclaimed. That keeps the page useful without converting old tooltips or datamined fragments into false certainty.