Source hierarchy
A versioned developer changelog can support “fixed in 1.006” for the exact issue it names. The Steam store supports release date, review descriptor, and current product details. The public player-count API supports only the moment it was queried. Community reviews support that players reported a symptom; they do not prove cause, prevalence, or a fix.
Community sample limits
The launch snapshot used the latest 100 English negative reviews returned by Steam on 28 September 2026. Negative reviews intentionally concentrate complaints and cannot represent all owners. Keyword counts overlap because one review may mention saving, progression, crashes, and performance. The sample is used to find repeated questions, not to calculate a defect rate.
Status language
- Official changelog: the developer published the record in a versioned update.
- Fixed in version: the changelog says the trigger was fixed; it is not a guarantee about every old save.
- Community report only: at least one player report is visible, but the reviewed official sources do not confirm the cause or status.
- Needs official confirmation: the symptom matters, but a safe, sourced fix is unavailable.
No invented fixes
Keeper Ledger does not publish registry edits, save replacements, file deletion, launch flags, mod instructions, or fabricated recipes. When an official note gives no recovery procedure, the page says so. On Steam PC 1.006, the safest escalation route is the in-game bug report function described by the developer.
Corrections
Records should change when a new official patch names the issue, a source disappears, or wording overstates the evidence. Each update should preserve the prior version context instead of silently turning a community report into an official one. The site stores no report form and receives no player files.