PATCH TRACKER

Saros UpdatePatch Notes and Known Issue Tracker

Use Saros Update only for changes that can affect a current route: patch notes, known issues, gameplay changes and verified fixes. If a claim is not official or reproducible, do not rebuild your run around it.

Official notes firstNo unverified patch claimsKnown issue riskRoute impact

On-Page Jump Navigation

Latest Update Brief

Act only when a patch note or verified issue changes a real route decision. Rumors do not deserve a build change.

FieldCurrent Update
Latest UpdateNo official gameplay patch notes tracked yet
StatusFramework ready
Source RuleOfficial notes first; no unverified patch claims
Player ImpactPending first sourced patch or issue list
Known IssuesTrack only reproducible or sourced issues

Top Rules Before You Change A Route

01

Patch notes

Wait for official notes or explicit proof before changing advice.

02

Known issues

Require reproducible evidence before changing a route.

03

Community reports

Treat as warning signals until confirmed.

Patch Trust Rules

When release, platform or named-system facts conflict, trust PlayStation, Housemarque and PlayStation Store before any rumor.

Treat launch-week route advice as a starting read, not a permanent order. Exact values need screenshots, direct play or repeatable proof.

For procedural or randomized systems, plan around behavior. Do not bet a run on fixed maps, caps or drop tables that have not been proven.

Known Issues and Workarounds

Do not change a build for a Saros known issue until official confirmation or repeatable evidence exists. If the bug cannot be reproduced, keep the route stable.

Workaround Labels

Official workaround
Reproducible workaround
Community signal only

Player Impact

New players

Hold your build until a patch or known issue actually changes this route.

Progression players

Hold your build until a patch or known issue actually changes this route.

Platinum cleanup

Hold your build until a patch or known issue actually changes this route.

Update History

VersionStatusNotes
LaunchBaselineUse release facts and first-run routing as the starting context.
First tracked patchPendingAdd only after official notes or verified evidence.

Data Requirements

First official patch notes

Known issue confirmations

Version history rows

Player impact analysis

Saros Update FAQ

Can I treat Saros Wiki&Tools as official?

No. Use Saros Wiki&Tools for route decisions, risk calls and cleanup planning. Use PlayStation, Housemarque and PlayStation Store when you need official release, platform or edition facts.

Why do some rows say testing in progress?

Because weak certainty wastes runs. If exact node costs, collectible counts, spawn rules or boss attacks are not proven, the safer move is to mark the risk instead of pretending the number is final.

Why is Saros Update sparse?

Because fake patch notes are worse than no patch notes. Use Saros Update when official notes or verified issue data can change a real run decision.

Will Saros Update list community bug reports?

Only when a report is reproducible or clearly labeled. Do not upgrade raw rumor into a route fact.

What counts as an official Saros patch source?

Official patch notes, PlayStation messaging, Housemarque channels or store-side update notices are the priority sources for version changes.

Should I use the release page or the update page after launch?

Use release for platform, edition and store facts. Use update for patch notes, known issues and any gameplay changes that affect current runs.