Documented Sephiria builds
The collected build pages name Frozen Smelt, Formless Dance, Minigun, Guardian Greatsword, Infinite Elemental Bolt, Biryuu Katana, and Planet Retest Blueprint. Each record describes a route that someone assembled under a particular version and reward sequence. The list is useful for learning interactions, but it does not prove that one route is the strongest choice for every player or patch.
Edeyie Sephiria build videos
These recent Edeyie uploads are embedded as playable examples, not official rankings. They show different weapon and Artifact directions under specific 1.0 runs; use the live tooltip and current reward pool before copying a route.
Three examples show how a name maps to a route. Frozen Smelt is recorded as Dagger into Sleeping Frost and then Frozen Smelt. Formless Dance is recorded as Staff into Throwing Spear and then Formless Dance, while Minigun follows Heavy Crossbow into Unstable Lightning Mark and Minigun. The current in-game Anvil and tooltip must confirm names and prerequisites before a player commits resources.
| Recorded route | Weapon direction | Evidence boundary |
|---|---|---|
| Frozen Smelt | Dagger / frost branch | Community route; verify current names and effects |
| Formless Dance | Staff / Throwing Spear branch | Community route; translation and patch can change labels |
| Minigun | Heavy Crossbow / Unstable Lightning Mark | Community route; reload and firing behavior should be tested live |
| Guardian Greatsword | Greatsword defensive route | Named community setup, not an official tier placement |
| Infinite Elemental Bolt | Elemental projectile route | Requires its trigger and support pieces to be evaluated together |
| Biryuu Katana | Katana named-sword route | Current sheathe, MP, and branch text take priority |
| Planet Retest Blueprint | Retest / legacy record | No complete current 1.0 clear or public preset in the collected evidence |
Evidence labels matter
A video clear proves that a setup completed the recorded run under the conditions visible in that video. A community recipe documents a proposed set of pieces but may omit execution, reward order, or a complete clear. A legacy or retest blueprint is a hypothesis or older route that needs current-version validation.
Do not flatten those records into a single “best builds” list. A video may use a Costume, permanent unlocks, or patch behavior that is not obvious from its final inventory. A written recipe may be easier to copy but provide less evidence that it survives late encounters. This site keeps the label attached so players can decide how much confidence to place in a route.
Build from a reliable trigger
Begin with the action the weapon performs reliably: guarding, landing broad swings, parrying, firing from range, changing Katana state, or controlling an area with the Staff. The core Artifact or upgrade should activate from that action often enough to matter across ordinary rooms, not only in an ideal boss window. Supporting pieces should improve the trigger, its outcome, or the player’s ability to repeat it.
Then identify the constraint. Greatsword may need room and recovery protection; Crossbow needs a plan for reload windows; Dagger must enter close range safely; Katana divides attention between state and MP. A build becomes coherent when its support solves that weapon-specific problem instead of collecting unrelated bonuses.
Place Artifacts and Tablets as a system
The inventory is part of the build rather than a passive storage screen. Artifact shapes create gaps and compete with future rewards, and Tablets care about adjacency. Before taking a piece, test whether it can connect to the intended Artifact without disconnecting something more important.
Keep the core relationship legible. If several Tablets support one Artifact, arrange them so a later move does not accidentally break two connections. If a secondary effect forces the entire inventory into an awkward layout, compare its real contribution with the flexibility lost by using those cells.
Choose a fallback before the route fails
Reward randomness means a named final form may never appear. A fallback is the version of the build that still clears rooms using earlier upgrades and common support. Decide which pieces are essential, which are interchangeable, and which only improve the ceiling after the engine already works.
For a Crossbow route, the fallback may preserve ranged control and safe reload timing without reaching Minigun. A frost Dagger route can still value reliable control and close-range access if Frozen Smelt does not arrive. The point is not to invent substitute names; it is to keep solving the same combat problem with the rewards actually offered.
Match the Costume to the route
The captured v1.0.24 database records 27 playable Costumes, and their effects can change starting items, stats, Dash behavior, MP, damage, inventory, or resource rules. That makes Costume selection part of a build’s starting assumptions. A route demonstrated on one Costume may feel different when another begins with a different resource or mobility rule.
Record the Costume with any shared build, and separate its contribution from the weapon and Artifact engine. Appearance variants are cosmetic records, not additional rulesets. Because Costume effects and unlock conditions can change, use the current selection screen rather than copying old numeric values from the archive.
Test a build honestly
Write down the game version, Costume, weapon path, core trigger, essential Artifacts, Tablet layout, and known fallback. Note whether the evidence is a full clear, partial clear, recipe, or retest. That information makes a route reproducible and prevents a successful screenshot from being mistaken for a complete guide.
Test ordinary rooms as well as bosses. A build that creates spectacular boss damage but cannot survive mixed enemy waves has an access or consistency problem. Conversely, a safe clearing engine may need a specific answer for an invulnerable phase, multi-part target, or dense projectile pattern.
When to abandon the preset
Preset strings found in build communities describe configurations; they are not reward redemption codes. They also do not guarantee that the required pieces will appear in the current run. Use a preset as a reference for relationships, then compare it with the live inventory and current tooltip.
Abandon the exact recipe when it asks for unsupported pieces, breaks a stable adjacency network, or ignores the run’s immediate survival problem. The best available choice is contextual. The collected routes are most valuable when they teach why an engine works, because that reasoning remains usable when rewards or balance change.