Changelog.ggBeta
HomeGamesUpdatesPricingMethodology
Steam News26 April 20262mo ago

Alpha v0.57.20 Hotfix

Usurper Reborn v0.57.20 - Save Repair Visibility (Hotfix) Hotfix for v0.57.19. The auto-repair option added in v0.57.19 wasn't actually appearing for some affected players.

In this update4

Full notes

Full Usurper Reborn update

Read the full published notes in a cleaner layout. The original post stays linked below.

What changed

1 fix3 additions2 changes0 removals
  • Balance
  • Gameplay
  • Fixes
fixedUsurper Reborn v0.57.20 - Save Repair Visibility (Hotfix)Hotfix for v0.57.19. The auto-repair option added in v0.57.19 wasn't actually appearing for some affected players. The repair code worked, but the menu logic that decides when to show the [R] option missed several common error paths, so players never got the chance to use it.
addedWhat was wrongAfter picking a recovery file that ALSO failed, the menu re-rendered with the ORIGINAL error message instead of the new failure - so even if the recovery file OOMed, the menu didn't update its option list.
changedWhat's fixedThree layers of defense so [R] reliably appears whenever it could possibly help:
changedWhat's fixedSynthetic short-circuit messages now include OOM-detection keywords so clicking a [RECOVERY]-tagged save shows [R] on the first menu entry, not after one futile recovery attempt.
addedWhat's fixedRecovery-file failures now propagate the new error when the menu re-renders. If your backup OOMs after your primary failed for a different reason, [R] now appears.
addedWhat's fixedFile-size fallback - if no error string matches, the menu now also scans the primary save and every recovery candidate file. Anything over 10 MB triggers [R] regardless of the error text. This catches every future case where a new error path doesn't use the exact magic phrasing.

Usurper Reborn changes

fixedHotfix for v0.57.19. The auto-repair option added in v0.57.19 wasn't actually appearing for some affected players. The repair code worked, but the menu logic that decides when to show the [R] option missed several common error paths, so players never got the chance to use it.
addedAfter picking a recovery file that ALSO failed, the menu re-rendered with the ORIGINAL error message instead of the new failure - so even if the recovery file OOMed, the menu didn't update its option list.
changedThree layers of defense so [R] reliably appears whenever it could possibly help:
changedSynthetic short-circuit messages now include OOM-detection keywords so clicking a [RECOVERY]-tagged save shows [R] on the first menu entry, not after one futile recovery attempt.
addedRecovery-file failures now propagate the new error when the menu re-renders. If your backup OOMs after your primary failed for a different reason, [R] now appears.

Usurper Reborn v0.57.20 - Save Repair Visibility (Hotfix)

Hotfix for v0.57.19. The auto-repair option added in v0.57.19 wasn't actually appearing for some affected players. The repair code worked, but the menu logic that decides when to show the [R] option missed several common error paths, so players never got the chance to use it.

What was wrong

The recovery menu only showed [R] Auto-repair when the load failure error message contained specific phrases like "Not enough memory" or "too large." But three of the most common ways a player ends up at the recovery menu produced different error text:

  • Clicking a save tagged [RECOVERY] in the load list (the most common path for affected players) used a generic "failed to parse during listing" message that didn't trigger detection.

  • After picking a recovery file that ALSO failed, the menu re-rendered with the ORIGINAL error message instead of the new failure - so even if the recovery file OOMed, the menu didn't update its option list.

  • Pure string matching is fragile - any error path that didn't use the exact magic words slipped through.

What's fixed

Three layers of defense so [R] reliably appears whenever it could possibly help:

  • Synthetic short-circuit messages now include OOM-detection keywords so clicking a [RECOVERY]-tagged save shows [R] on the first menu entry, not after one futile recovery attempt.

  • Recovery-file failures now propagate the new error when the menu re-renders. If your backup OOMs after your primary failed for a different reason, [R] now appears.

  • File-size fallback - if no error string matches, the menu now also scans the primary save and every recovery candidate file. Anything over 10 MB triggers [R] regardless of the error text. This catches every future case where a new error path doesn't use the exact magic phrasing.

If you tried v0.57.19 and didn't see the repair option

Launch v0.57.20, go to Load Game, click your character. The recovery menu now shows [R] Auto-repair the bloated save file (recommended) right away. Press R and it will walk through your backup, autosaves, and emergency saves, trimming each one down until one loads cleanly.

Tests

All 12 save-repair tests from v0.57.19 still pass. Full project suite: 653 tests, all green.

As always, please report any issues with these changes via the in-game [!] Bug Report option or in our Discord.

Source

Steam News / 26 April 2026

Open original post

Changelog.gg summarizes and formats this update. How we read updates.