Path of Idle Save Error & Rollback: Safe Recovery Checklist

Patch 1.1.3 lets a newly created save inherit Codex progress from another save. A save created before the patch receives one opportunity, unless its current Codex progress is already the best available. Treat the choice as a one-time progression feature, not a backup, cloud-restore or merge tool: the announcement does not document undo behavior, merge precedence, deleted-save recovery or a way to repeat the choice.

Continue with: review the current patch boundary · check the Equipment Codex workflow

Source: Official version 1.1.3 Codex Inheritance rules ↗

A current Steam discussion reports a character record disappearing after roughly 270 hours. That report establishes a serious player symptom, but it does not establish one root cause or a guaranteed recovery method. Stop creating new saves, record the selected Season and slot, preserve separate local and Steam Cloud copies, and compare timestamps before changing anything. Version 1.0.11 added nine save slots per Season, so verify that the intended Season and slot are open. The Windows path documented later on this page is explicitly for the Demo; do not assume the retail save uses the same 301/offlinePlayer.bin location unless the developer confirms it for your case.

Source: Current official Steam discussion list ↗

Stop before repeatedly launching, saving, deleting, or replacing files. Record the installed version, active Season, selected save slot, last known-good play time, and whether Steam Cloud reports a sync conflict. Preserve separate copies of the current local file and any official Steam Cloud download before comparing timestamps. Version 1.0.11 added nine save slots per Season, so first confirm that the game opened the intended Season and slot. A rollback topic in the Steam community establishes that the symptom concerns players, but there is no current developer statement proving one universal cause or guaranteed recovery method. If the correct slot and copies remain unclear, use the official Steam discussion and include the evidence above instead of trying a third-party save.

Source: Official version 1.0.11 update ↗

The developer's confirmed local Demo save path is: C:\Users\<YourPCName>\AppData\LocalLow\SmallMill\PathOfIdle\301\offlinePlayer.bin AppData and SmallMill may be hidden. If you changed computers, the new machine will not have this Demo file. Download the Demo save from Steam Cloud, close the game, preserve a copy of any existing offlinePlayer.bin, and only then place the recovered file in the 301 folder. Reopen Steam and the full game after the file operation completes. Do not download another player's save or a third-party executable.

Source: Developer save-recovery instructions ↗

Small Mill stated that Demo data would be retained for the full version. If the transfer is missing, avoid repeatedly creating new saves because each new local state makes it harder to identify the correct file. Confirm you are using the same Steam account, inspect Steam Cloud for the Demo file, back up both the local and downloaded versions, and use the developer-confirmed Windows location. If the timestamps or files remain unclear, stop before overwriting and report the account, PC change, and file timestamps through the official Steam discussion.

The developer added a Hide Combat Effects setting and optimized combat rendering during the final demo updates. Disable combat effects first when large fights stutter. Keep the game and graphics driver current, close overlays for a comparison run, and lower the refresh-rate setting if needed. An earlier issue where refresh-rate settings did not work was fixed in demo version 1.0.0.0.

Version 1.0.7 fixed possible Baptism errors and possible black lines on the Chapter 20 map. Update and restart before trying destructive fixes. Version 1.0.5 also changed Blessing Talent Points; reset Talents after updating as the official note requests. A changed talent display after Inspire may likewise be resolved by 1.0.7.

Record the game version, operating system, the exact screen and action, whether the issue repeats after restart, and a screenshot or short video. For progression issues, include the relevant chapter, town building, class, and item or skill name. Link to the official announcement or discussion rather than relying on an old third-party fix. Never download replacement save files or executables from an untrusted guide site.

Start with the reversible steps: confirm the installed version, wait for Steam Cloud to finish, restart the game and Steam, and reproduce the issue once with overlays or optional visual effects disabled. Change one setting at a time and note the result. Do not delete saves, reinstall the operating system, or run a third-party repair executable as an early step. If reinstalling becomes necessary, first confirm how the game and Steam Cloud protect the current save and preserve a backup through an official or well-understood method.

A missing button, changed cost, or different Talent total is not always corrupted data. Compare the installed version with the latest developer note and read the current tooltip. Version 1.0.5 intentionally changed Blessing Talent Points and required a Talent reset, while 1.0.7 fixed Baptism and talent-slot problems. If the behavior matches a documented change, update the build or workflow. If it contradicts the current note and reproduces after restart, prepare a focused report with the smallest sequence that triggers it.