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.
Act only when a patch note or verified issue changes a real route decision. Rumors do not deserve a build change.
| Field | Current Update |
|---|---|
| Latest Update | No official gameplay patch notes tracked yet |
| Status | Framework ready |
| Source Rule | Official notes first; no unverified patch claims |
| Player Impact | Pending first sourced patch or issue list |
| Known Issues | Track only reproducible or sourced issues |
Wait for official notes or explicit proof before changing advice.
Require reproducible evidence before changing a route.
Treat as warning signals until confirmed.
| Source | Use | Priority |
|---|---|---|
| PlayStation Blog - modifiers and gameplay systems | Official | Trust before acting |
| PlayStation Store - Saros product page | Store | Trust before acting |
| Housemarque - Saros official game page | Official | Trust before acting |
| PowerPyx trophy roadmap | Media guide | Trust before acting |
| PowerPyx boss guide | Media guide | Trust before acting |
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.
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.
Hold your build until a patch or known issue actually changes this route.
Hold your build until a patch or known issue actually changes this route.
Hold your build until a patch or known issue actually changes this route.
| Version | Status | Notes |
|---|---|---|
| Launch | Baseline | Use release facts and first-run routing as the starting context. |
| First tracked patch | Pending | Add only after official notes or verified evidence. |
First official patch notes
Known issue confirmations
Version history rows
Player impact analysis
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.
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.
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.
Only when a report is reproducible or clearly labeled. Do not upgrade raw rumor into a route fact.
Official patch notes, PlayStation messaging, Housemarque channels or store-side update notices are the priority sources for version changes.
Use release for platform, edition and store facts. Use update for patch notes, known issues and any gameplay changes that affect current runs.