Skip to content
Nivalis NightsIndependent game Wiki

PC & saves

Large saves, slow loading and missing old reviews after Update 5

Update #5 + October 16 balancing · sources checked October 22, 2026

The short answer

Update 5 reduces the individual review history stored in saves while retaining lifetime review statistics and achievement counting. It keeps the last month of individual reviews for your venues and recent reviews for others. Older individual entries no longer being available is therefore different from all your review progress being lost.

The developer observed some late-game files becoming up to 50% smaller. That is an example, not a guaranteed reduction for your save or a promise that every loading problem is repaired.

Nivalis Nights / Saves and review history

A shorter list is not every review lost.

  1. Individual owned-venue reviews

    Last month retained in the save.

  2. Lifetime totals

    All reviews still count for statistics.

  3. Save-failure popup

    Check separately from history trimming.

Wiki explainer · not an in-game screenshot. Up to 50% smaller was a developer example, not a guaranteed result. Sources and version ↓
On this page

Check the missing information before calling it data loss

Individual history and aggregate progress
What you are checkingUpdate 5 boundary
Your individual venue reviewsLast month retained in the save.
Other venues’ individual reviewsRecent entries retained.
Lifetime statistics and achievementsAll reviews still count.
Lifetime individual review listThe full historical list cannot be displayed.

Existing saves are converted automatically according to the update. Do not delete older saves or restart solely to force a smaller file. First compare the current totals with the specific older review entries you expected to see.

A save-failure popup needs a different response

Update 5 adds an explicit popup when saving fails and fixes a story-sleep autosave issue. A smaller review-history window is not evidence that a failed save succeeded.

  1. Read and record the exact popup and current build.
  2. Keep existing known-good saves; avoid overwriting your only copy while investigating.
  3. Use the game’s visible save/load interface to confirm which save actually exists.
  4. Record the action before the failure, such as a story-triggered sleep, separately from ordinary loading time.

The notes do not establish a universal save-folder path, cloud-sync repair command or safe file-editing procedure. None is invented here.

Compare loading under the same conditions

The update includes startup/loading and memory work and reduces NPC-related stutter at hour changes. Record the save, location, game version and time to reach a playable scene before comparing. A frame hitch while new NPCs appear and a slow save load are different observations.

Change one relevant setting at a time and retain a known-good save. An installation error, driver fault or slow storage device cannot be diagnosed from review-history trimming alone. On Deck, use the dated settings and menu-control guide without treating its player FPS reports as a PC benchmark.

What this check can establish

You should be able to distinguish a retained lifetime total, an intentionally shorter individual review list, a visible save failure and a measured loading delay. Keep those observations separate in any report.

This guide does not promise recovery of a missing save or restoration of every historical review entry. The release notes describe the retention boundary and specific fixes, not a universal data-recovery tool.

Sources & version

Use the version and source dates listed for this article. Developer fixes, dated creator demonstrations and player reports are distinguished; a current review does not turn an older source into a new-build gameplay test. We do not claim our own gameplay reproduction.