Updates are part of the guide, not an afterthought. Sephiria has an Early Access history and a public 1.0 release listed on Steam on 31 July 2026. A player report written before launch can still explain a question, but it cannot automatically prove the current item pool, balance, achievement behavior, or progression route. This hub keeps official announcements, patch notes, and version history distinct so a guide can say exactly which evidence it used.
Start with Steam
Use the store and official announcements for release and product-scope facts.
Find the changed system
Separate a balance change from a new feature or a bug fix before updating advice.
Label the era
Mark Early Access, launch, and later versions so old guides do not look current.
Retest the page
When a mechanic changes, check the affected weapon, Artifact, Tablet, boss, or achievement page.
What belongs in an update log
The Official Updates Guide records a dated source, the product it applies to, and the systems a player should retest. The Patch Notes Guide explains how to turn a note into a page change. The Version History Guide preserves the boundary between Early Access and launch without pretending that every old detail remains valid.
Use a narrow entry. “Balance changes” is not enough; say whether the note affects a weapon, an Artifact interaction, a Tablet rule, a boss, or a platform. If an official note is silent, do not fill the silence with a community rumor. Add a secondary lead in a clearly marked section and keep the guide’s recommendation cautious until the live game confirms it.
Retest workflow
When an update mentions a system, reproduce the smallest test that can show a change. For a weapon, use the same target and range. For inventory, use the same arrangement and record the visible effect. For a boss, compare the telegraph or recovery window. For achievements, check the official description and the client after the condition. Write down platform and mode because online co-op and single-player behavior can diverge.
After the test, update the page’s version scope and evidence label. If the result is unchanged, keep the original advice but note that it was retested. If the result is uncertain, remove an exact claim rather than preserving a stale number. This is slower than copying a patch headline but protects players from a misleading guide.
Source hierarchy
The Steam store, Steam announcements, and TEAM HORAY’s official channels are first-party sources. Steam Community posts are useful for discovering questions and possible regressions, not for silently replacing official facts. The demo listed by Steam has AppID 2686970 and is excluded from this base-game site’s scope. Keep links explicit so future editors can audit why a page says what it says.
Keep an unresolved note visible until the live game or a later official source answers it. Removing uncertainty from the wording does not make the underlying behavior more certain; it only makes the guide harder to audit.
For that reason, a short pending note is preferable to a confident paragraph built from an unverified community summary.
A maintenance handoff
End each entry with the next owner: Weapons, Artifacts, Tablets, Builds, Chapters, Bosses, Multiplayer, or Achievements. Include the smallest retest that can confirm the change. This keeps the Updates hub actionable and prevents a dated announcement from remaining disconnected from the page where players feel its effect.
Separate release milestones
A release milestone answers when the product moved from one public phase to another. A patch note answers what changed inside a phase. Keep those records separate. Sephiria’s Steam page currently shows an Early Access history and a public 1.0 release on 31 July 2026. A guide written before that date can remain useful as historical context, but its exact balance and progression claims need a launch check.
Connect an update to a page
When a note touches weapons, send the editor to Weapons and Builds. When it touches inventory, send the editor to Artifacts and Tablets. When it touches an encounter, send the editor to Chapters and Bosses. When it touches a trigger, send the editor to Achievements. A cross-link is more useful than a generic statement that “the meta changed.”
Keep a change ledger
Record source URL, publication date, affected system, verification date, platform, mode, and editor decision. If the current game does not reproduce the note, mark it as unresolved and retain the official wording. This small ledger lets returning players see whether a page is current, historical, or waiting for a retest.
Reader-facing labels
Use a visible label for launch scope, current patch, historical Early Access, community lead, and pending retest. These labels should be short enough to scan but specific enough to prevent a historical sentence from looking like a current fact. When a change is confirmed, update the affected page’s version scope and preserve the old source in the changelog rather than deleting the audit trail.
An update page is successful when it answers “what should I check now?” The answer may be a weapon comparison, an inventory placement, a boss practice room, a co-op call, or an achievement confirmation. Link directly to that task and state whether the reader needs a new save, a new run, or only a retest of the existing route.