LootWiki

Sephiria Patch Notes

Four patches in one month. What each changed, and which of our guides it invalidated.

Why this section exists

Sephiria's version numbering is genuinely confusing, and it produces bad search results.

There is no published 1.0.20. The sequence runs 1.0 Update → 1.0.21 Hotfix → 1.0.22 → 1.0.23 → 1.0.24. Search for "Sephiria 1.0.20 patch notes" and you will find pages confidently listing changes for a patch that was never released.

Two further wrinkles make the record harder to read than it should be. The announcement titled "1.0 Update" carries the full 1.0.19 notes inside it — that is where all the substantive launch balance lives, not in a post named 1.0.19. And 1.0.21 contains a section titled "Additional Changes Missing from the 1.0.19 Patch Notes", documenting real balance changes retroactively, including the Sword & Shield Cleave cost drop that makes the starting weapon meaningfully better than Early Access guides describe.

What we track

Every 1.0 announcement from 1.0.19 through 1.0.30, what it changed, and — the part most patch-note pages skip — which of our own guides a patch invalidated.

When a change makes one of our pages wrong, we say so here rather than silently editing the page and pretending it was always correct. That matters in a game this young, where a strategy can stop working between two Tuesdays.

What the cadence tells you

Four patches in the eleven days after launch, with two and three day gaps between them. TEAM HORAY is shipping small, fast fixes rather than batching them into monthly releases, and marking community-requested changes explicitly with a carrot emoji in their own notes.

For a studio that spent fifteen months in Early Access before launching, that is consistent with how they ran the beta — which is a reasonable signal that reported bugs get addressed rather than accumulated.

Two things worth knowing right now

The artifact-stability era ended in August. Through 1.0.24 no artifact or tablet balance had moved since launch; then 1.0.26 repaired the Green Sawblade's stacking and 1.0.30 sent the Frozen Bow's arrows through walls. Inventory layout advice is still current — grid shapes and costs remain untouched through 1.0.30.

Multiplayer keeps receiving most of the attention. From invisible Halberd range and chapter-mismatch softlocks in the launch window to the revive temporary-HP rework in 1.0.26 and the Chapter 6 game-over freeze fixed in 1.0.29 — nearly every patch has carried co-op repairs. Update before organising a session.

One loose end

1.0.25 is referenced inside the 1.0.24 notes as fixing a Training Grounds freeze, but its own announcement never appeared in the feed. We are noting it rather than reconstructing what else it might have contained.

Status check: 1 September 2026

1.0.30 (20 August) is the newest patch. The quiet stretch we flagged after 1.0.24 broke on 13 August: six version numbers shipped across three announcements in eight days — 1.0.26/27, the 1.0.28 hotfix carrying 1.0.29, and 1.0.30 — then the feed went quiet again. The burst included the first genuine weapon-rule changes of the 1.0 era and three new interface languages; the full breakdown is on the 1.0.25 to 1.0.30 page. The pattern now reads as cycles: fire-fighting, silence, batch, silence. When the next announcement lands, this line changes.

How to verify a patch claim yourself

Auto-generated wikis routinely publish notes for patches that do not exist — the phantom "1.0.20" pages are the standing example. Checking takes under a minute and needs no account: open the game's Steam news feed, which lists every official announcement in order, and treat anything that is not there as unconfirmed. Two conventions help when reading TEAM HORAY's own posts: the carrot emoji (🥕) marks changes made from community feedback, and version numbers are only trustworthy inside the announcement body — titles sometimes lag (the post titled "1.0 Update" is where the full 1.0.19 notes actually live). If a claim traces to a translation of the Korean notes rather than the English post, we flag it here before relying on it — the two have disagreed before, most visibly on talent names.