Steam Cloud, Lost Saves and Other Known Issues in Yet Another Zombie Survivors

Work through these in order: identify your version, apply the fix the developer already shipped, and restore lost progress with the in-game backup option first. The cloud-file deletion note is explained, not handed to you as a command.

Based on the developer's Steam update notes for versions 1.0.1a through 1.0.2, checked 2026-11-15. Later updates may change these fixes.

Order matters here: several of the issues below were fixed by the developer itself, so the first question is whether your build already contains the fix. Do the non-destructive steps first and keep your save data intact.

Step 1 — Check your version, then the matching note

Open the main menu and read the version string. Then match it to the dated note:

If your build isWhat the developer's note says
1.0.2 or newerSteam Cloud sync fixed; Windows 11 "Failed to load il2cpp" launch errors should no longer be caused by Smart App Control
1.0.1b or newerSurvivors' aiming problems fixed; the Luck stat cap (previously 1000) was removed
1.0.1a or newerIn-game save backup restore is available from the Change Save Slot menu

If your build is older than the note that fixes your problem, the fix is the update itself — not a workaround. The full dated text is on the update notes page.

Step 2 — Lost progress: use the in-game restore first

This is the only documented recovery path, and it is inside the game:

  1. Open the Change Save Slot menu.
  2. Press T on keyboard or Y on controller to use the save backup restore function.
  3. Import the backup into an empty slot.

That is the 1.0.1a note's description of the function, including both key prompts. The 1.0.2 note adds that lost progress "can be restored easily" with the in-game backup system documented in the pinned Save backup information thread on the game's Steam Community hub — open the pinned posts there for the developer's full instructions rather than relying on a summary.

Three limits worth knowing before you click: the captured notes do not say how a backup is created in the first place, whether targeting a non-empty slot is refused or overwritten, or how many slots exist. So back up the slot you are about to touch outside the game before you restore into it — a plain copy of your save folder — and target an empty slot as the notes describe.

Step 3 — Steam Cloud still not syncing

The 1.0.2 note says sync "was not synchronizing properly, and that issue is fixed". It also says the problem can still happen because of faulty local files, and it names a one-time deletion of the /remote/ folder and the remotecache.vdf file as what that situation requires.

This page will not give you a delete command for those two names. The note prints the folder and file but never prints their full path, so no page — including this one — can tell you which directory on your disk it meant. Deleting the wrong remote folder destroys save data, and there is no undo.

A safe sequence instead:

  1. Close the game completely, including the launcher's background process.
  2. Copy your entire save directory to a separate backup location and confirm the copy opens / contains your slot files before continuing.
  3. Confirm the game still launches and shows your progress with the copy in place — you now have a restorable state.
  4. Only then read the developer's own instructions in the 1.0.2 post and in the pinned threads on the game's Steam Community hub, and follow the path they name — not a relative name quoted out of context.

If you cannot verify which folder the note refers to, stop at step 3. A cloud sync warning is recoverable; a deleted save folder usually is not.

Step 4 — The other changes worth knowing about

Luck stat cap. 1.0.1b removed the cap; the note states it "was previously a maximum of 1000". The 1000 figure is the old ceiling, not a current threshold, so do not plan builds around hitting it. The note does not say what Luck changes numerically.

Aiming. 1.0.1b lists Survivors' aiming problems as fixed, without describing the symptom or which Survivors were affected. If aiming still feels wrong on a 1.0.1b-or-newer build, that is outside what these notes cover, so report it rather than applying a workaround.

Level-up clarity. The same 1.0.1b hotfix made Weapon and Ability Skill Tree node levels visible on highlight or hover. If you are comparing options before spending a level, this is the change that made it possible.

What this page does not cover

No performance problems, crashes, installation failures, driver conflicts, or general diagnostic order appear in the captured notes, so this page does not walk through them. Where a fix is not in the list above, the developer's support channel is the right place to ask.

Sources