Horses of Hoofprint Bay: Stable Save Reverted From Day 230 to Day 65

Direct answer · November 10, 2026 original-source and version check

A player reported that a day-230 stable reverted to roughly day 65 even though some later horse names remained visible in save files. The developer's v1.0.2 improved crash backups but did not promise recovery of every already reverted save.

Jump straight to the steps ↓

THE TASK

Stable Save Reverted From Day 230 to Day 65

  1. 01

    Stop playing on the unexpectedly older state before it can overwrite another usable backup, and record the day number and last known successful session.

  2. 02

    Inspect only the game's officially exposed backup or recovery options first; preserve copies of all existing saves rather than swapping files based on a guessed path.

  3. 03

    Compare the date and expected progress of any recovery candidate, and report the mismatch with your save and crash history to the developer if no suitable recovery is offered.

Source-checked task schematic · Decision points

Save reverted from day 230: preservation before restore

Decision points

Source-backed editorial schematic, NOT gameplay screenshot or scale map. It is not an in-game screenshot and not a map drawn to scale.

Open the specific source evidence ↗

Prerequisite

A first-person report describes day 230 reverting to roughly day 65, not an established universally recoverable file.

Success check

A verified backup contains the expected progress before any restore choice is made.

01

Freeze

Stop progressing on the unexpectedly old save

02

Compare

Record the displayed day and the previously reached day

03

Preserve

Make safe copies of every available save/backup version

04

Official recovery

Inspect the game-exposed backup options and their dates

05

Support

If recent progress is absent, report the save state and crash history to developer

IMPORTANT LIMITS

What if your result is different?

The original thread has no proven universal restoration method; visible horse names alone do not establish that the remainder of day-230 progress is recoverable.

EVIDENCE

Sources for Stable Save Reverted From Day 230 to Day 65

Evidence and version: November 10, 2026 original-source and version check

Treat a day-230-to-day-65 rollback as potential data loss

The original player described a long-running stable suddenly displaying day ~65 instead of ~230, while some later horse names remained visible in files. That mixed state makes it unsafe to pick a single backup based on its filename or to copy fragments between saves.

The November 8 v1.0.2 patch added exception handling and validation files for backups, lowering future failure risk. It does not establish a recovery procedure for the exact old day-230 case, nor guarantee that an existing “backup” contains the newest valid stable state.

Before testing anything: close the game, preserve separate byte-for-byte copies of all current/local/Steam Cloud variants, record filenames/timestamps/size, then only test a game-supported restore in a safe copy or ask the developer to examine the files. Completion: a candidate restore loads with the expected day, horses and inventory intact. Never overwrite a unique remaining copy to follow a fabricated universal “restore save” walkthrough. Real UI evidence must redact private paths/accounts and include build, restore screen, and observed day before/after.