Sephiria Bosses Guide: Learn Current Warnings and Phases Without Guessing

Why the boss answer has to be version-aware

TEAM HORAY's 1.0 release added Chapter 6, two new bosses, one new mini boss, and the ending. The official announcement stream has then continued to adjust or fix boss warnings, projectile patterns, hitboxes, and fight-state issues. A guide that acts as though an old recording shows one permanent phase script can therefore teach the wrong visual cue or leave out a newer encounter.

The player-maintained Sephiria Compendium groups bosses and mini-bosses by Chapters 1 through 6, including the late-game Qliphoth encounters. That is useful for identifying which chapter context a name belongs to. It is a community reference, however, so use it to orient yourself and let the current fight, game text, and official patch notes settle a mechanic that affects your run.

Read an encounter as a sequence of decisions

A boss attempt does not need a complete memorised route to teach you something. Start with the decision immediately before the hit: did you stand too near, spend a movement option too early, lose track of a warning, commit to a weapon action during a dangerous window, or misread a transition? One answer is enough to make the next attempt better.

Keep the weapon and board as familiar as possible while learning a new encounter. A large rebuild at the same time as a first boss attempt makes the result hard to interpret. First learn the warning and your safest response; later, test whether a different upgrade, Artifact, Tablet, or Talent makes that response easier to execute.

A three-step boss learning record

Write a small record after each serious attempt. This gives a player a reusable guide to their own current version instead of a pile of guesses about what a boss was supposed to do in someone else's clip.

Do not turn an observation into a universal claim after one result. The useful test is whether the same warning and response remain readable when you meet that encounter again.

• 1. Name the chapter, boss or mini-boss shown by the current encounter, plus the mode and player count if you are in co-op.
• 2. Isolate one warning, projectile pattern, transition, or positioning error that ended the attempt, then choose one response to test next time.
• 3. Record the phase or moment where the response worked or failed, and keep the next run otherwise comparable before changing the whole build.

Treat phase changes as new questions

Official post-release notes mention adjustments to a final-boss phase, fixes to a Qliphoth safe-zone interaction, and fixes to encounter states when a boss is stunned or a transition occurs. Those notes confirm that a later phase can behave differently from the opening exchange, and that fight information can change through patches.

When a transition arrives, stop applying the earlier solution automatically. Look for the new screen space, movement demand, warning timing, or target priority the next phase presents. If you cannot name it yet, make survival and observation the goal of the next attempt rather than forcing damage through a pattern you have not understood.

Connect the boss lesson to the rest of the run

A clean boss lesson tells you what to work on elsewhere. If you lacked room to move, revisit the weapon rhythm or movement choices. If an active board never came together, revisit Artifact and Tablet decisions. If a Hard Mode condition changed the whole test, learn the encounter in a simpler condition before treating a failure as a build verdict.

For completion goals, use the official Steam achievement list for the public boss milestones and verify the result there after the run. Do not infer a hidden achievement trigger from a boss name or turn a visible title into a promise that the same condition works in every mode.