SEPHIRIA / REFERENCEv1.0.31

Sephiria Builds for Different Run Goals

Compare documented weapon and artifact interactions, choose a run direction and adapt your setup when rewards change. Includes 1.0.31 route notes.

Build route quick reference

Route to investigate Required connection Decision before committing
Cleave-triggered lightning Blinding Silence + Thunder's Earring Do you have the named Artifact and use Cleave reliably?
Orbiting cold effect Garden of Needle Ice + Ice Vine Is the enabling Artifact already available?
Reload-supported Crossbow Crossbow + Stiff Crank Will your normal combat pattern complete reloads?
Element-led weapon attacks Prismatic Magic Wand Which elemental damage value is highest?
Health conversion Bloodletting Gearblade Can you explain the temporary HP conversion first?

These are mechanism-based route candidates, not tested complete builds. The named interactions are documented in TEAM HORAY's 1.0.31 announcement. Clear rates, final inventories and required drop locations: not available.

Core, support and fallback decisions

Direction Core evidence Support to evaluate When to postpone
Lightning trigger Cleave activates the named earring Ability to keep using that action The earring is missing
Cold orbit The named upgrade changes Ice Vine behavior A layout that keeps the effect useful You cannot identify the changed activation
Reload route Stiff Crank evolves after 50 completed reloads Equipment that fits the reload cycle Your actual play rarely reloads
Prismatic route Highest element controls the attack element; a tie produces Chaos A deliberate choice of leading element You are assuming Physical Damage drives the attack
Bloodletting route Excess Max HP at activation becomes damage under the described conversion A measured understanding of the health state You are relying on an unverified safe HP threshold

The table explains dependencies, not a guaranteed shopping order. “Support” is an editorial evaluation prompt. It does not assert an additional hidden interaction or a specific optimal stat value.

Start a route from what the run gives you

  • Identify the enabling pair before spending around it. For the Cleave route, the weapon's explicit reference to Thunder's Earring is the reason to investigate the pairing. Merely finding a lightning-related object is not equivalent to owning the named Artifact. Inspect the current inventory and decide whether the interaction exists now. If only the weapon is available, treat the completed route as a possibility rather than counting its eventual damage in your current plan.

  • Keep the core smaller than the finished build. A route description should tell you which pieces make its defining behavior occur. Everything else should earn a separate explanation. This makes it possible to adapt when the offered rewards differ from a screenshot. If you cannot explain why an object is included, put it in the optional category until you can test its contribution. Avoid making an ordinary improvement sound like a mandatory prerequisite.

  • Choose a problem for the next reward to solve. After establishing an interaction, watch what limits it. Perhaps the relevant action is awkward to repeat, perhaps you are uncomfortable at the required distance, or perhaps the effect is strong only during a brief opening. These are different problems. Evaluate the offered choices against the one you actually observed instead of automatically selecting whatever shares the build's element or visual theme.

Run the Cleave and earring experiment

  • Begin with the action, then add the payoff. Use the weapon's ordinary actions first so you recognize Cleave separately from normal attacks. With Blinding Silence and the named earring present, repeat the action and inspect the activation described in the patch. The test is whether the relationship works as stated in your current version. It does not establish boss damage, maximum output or an ideal inventory. Keep other triggered effects out of the initial comparison where possible.

  • Watch repetition under pressure. Once the interaction is recognizable, try a short sequence that includes moving and recovering between activations. A route can be easy to demonstrate while still feeling difficult in actual combat. Note which part interrupts you: the input, resource availability, positioning or attention. Choose subsequent support around that interruption. This recommendation follows from the dependency structure; it is not a published speedrun route or a promise of a clear.

Give Crossbow a complete cycle

  • Count reloads as part of the route. Stiff Crank's documented evolution uses completed reloads, so a test that shows only an already loaded attack leaves out a defining part of the setup. Observe the interval from one ready state to the next. Record whether you can repeat that interval comfortably, and check the Artifact after its condition is fulfilled. No exact dungeon location for acquiring the crank has been verified here.

  • Do not merge every ammunition upgrade into one build. M-9200 is documented around Ammo Compression, while the crank concerns reload behavior. They can be investigated in the same weapon context, but the presence of both names does not prove an optimal combination. Test the contribution of each before building a fixed list around them. An enhancement to one moment in a cycle can feel different from an improvement that affects how often you reach that moment.

Handle conditional scaling deliberately

  • Inspect the leading element on the Prismatic route. Its rule is based on the highest elemental value, with a special outcome when values tie. That means changing equipment can change more than the size of a number. Compare the displayed state before and after a swap. Do not intentionally force a tie unless you understand why that outcome helps the current plan; this guide has no benchmark showing that a tie is universally better.

  • Treat health conversion as its own experiment. Bloodletting deserves a separate test because the named special changes a health state as part of its payoff. Watch activation, the active period and the ending state. Avoid bringing over assumptions from ordinary healing or maximum-health bonuses without checking what the special actually does. The official description establishes the conversion, but this site has no tested minimum-health recommendation or survival guarantee for the route.

Preserve a usable fallback

  • Keep a functional present-tense plan. A fallback answers what you can do before the missing piece arrives. It should describe an attack you can currently repeat with equipment you currently possess. If the core never appears, that fallback may become the final direction. This does not mean every choice can be reversed; read the upgrade screen before committing. The purpose is to prevent a speculative future pairing from crowding out the needs of the next encounter.
BEFORE YOUR NEXT RUN

Frequently asked questions

Are these complete endgame builds?

No. They are documented interactions with practical evaluation routes. Full tested inventories, clear times and current-version success rates are not available. The distinction is deliberate: an official synergy is useful evidence, but it does not prove that a complete run assembled around it outperforms alternatives.

Should every item match my element?

Judge the actual effect and trigger. Matching an element can be relevant, but a resource or survival problem may need a different kind of solution. This guide recommends assessing the contribution to your active plan rather than using a shared color or name as sufficient evidence of synergy.

Where can I test a candidate setup?

The 1.0.31 update documents a Comprehensive Training Grounds accessible from the Training Grounds entrance. Its inventory lets you try already unlocked items. Use it for interaction checks, then keep expedition observations separate because obtaining and operating equipment during a run is a different challenge.

What should I record when sharing a build?

Include the game version, weapon upgrade, active Artifacts, inventory arrangement, costume, relevant progression choices and the situation tested. Describe the repeated action and any missing dependencies. Report a successful attempt as an attempt, without turning it into a statistical claim about reliability.