KOTAMON Save Not Working: Upgrades Reset and Safe Recovery Steps
Diagnose KOTAMON save-menu failures, missing upgrades, and lost progress with version-aware checks that protect your existing save.
Updated 2026-08-26 · Evidence-backed · Spoiler-aware
Section 01
Identify which save problem you actually have
Players are using the phrase 'save not working' for at least three different symptoms: the save window appears underneath another menu and cannot be clicked, a retail save reloads with cards or figurines intact but money and upgrades missing, or an imported demo save retains cards while older progression is gone. Those symptoms do not necessarily share one cause. Before changing files, write down which parts survived, whether the save started in the demo or retail release, and the last normal action before exiting. A precise symptom is the difference between diagnosing a planned migration reset and risking a still-recoverable retail save.
Section 02
Demo migration and retail progress loss are different
The developer's first major post-launch announcement says demo money and upgrades were intentionally reset after the economy was rebalanced, while card collection progress was preserved. If that exact pattern appears on a save that began in the demo, it matches an announced migration decision. Community reports also describe retail sessions in which purchased upgrades or money disappeared after reloading, including saves created after release. That second pattern should be treated as a possible bug rather than being dismissed as demo migration. Record the save origin before following advice from either group.
Section 04
Check cards, collectibles, cash, and upgrades separately
Do not decide that the entire save is gone from one empty upgrade panel. On reload, inspect the card binder, figurine display, other collectible counts, cash total, and every upgrade category as separate fields. Multiple Steam reports describe cards or figurines surviving while upgrades reset, and one report says both upgrades and money failed to persist. This split state is important because it suggests partial persistence rather than a completely missing slot. Photograph the surviving and missing categories before starting another run so a later save does not overwrite the clearest comparison.
Section 05
Use the safest verification order
First, confirm Steam has finished updating KOTAMON and read the newest developer announcement. Second, return to the title screen through normal menus if the interface still responds. Third, restart Steam once and load the same slot without buying, selling, repairing, or collecting anything first. Fourth, compare the same categories again. Stop if the state changes unexpectedly. These steps are reversible and create a clean record. They do not guarantee recovery, but they avoid turning a display, synchronization, or version problem into permanent loss through aggressive experimentation.
Section 06
Do not delete slots as a first-line fix
A community commenter reported deleting visible slots and starting over, after which saving appeared to work. That is one player's workaround, not an official recovery procedure, and the same comment confirms the earlier progress was lost. Deleting slots, disabling Steam Cloud, replacing local files, or copying unknown saves can remove evidence and make recovery harder. This guide therefore does not recommend those actions. Preserve the current state until the developer supplies a documented backup or recovery path, especially if the binder or collectibles still contain hours of progress.
Section 07
Protect the next session before investing hours
Until the affected build is clearly resolved, test persistence with a deliberately short session. Note current cash and one upgrade level, perform a small normal action, save through the menu, return to the title screen, and reload once. Do not grind for several hours merely to test whether the bug remains. If the same field resets, stop and report it. If it persists, that single test still does not prove every later save will be safe, but it gives more useful version-specific evidence than an uninterrupted long session followed by an ambiguous failure.
Section 08
Write a reproducible report for the developer
Use a title that names the missing state, such as 'Retail save reloads cards but resets upgrades.' Include the game build or update date, whether the slot began in demo or retail, Windows version, input method, display mode, and a numbered sequence from loading to saving and reloading. State exactly which categories persisted. Link an existing matching Steam thread rather than creating duplicates when possible. Do not post personal account data, cloud tokens, email addresses, or full local paths containing your real name in a public discussion.
Section 09
What current evidence does and does not establish
Steam discussions establish that several independent players encountered save-menu layering, missing retail progress, and upgrade resets around launch. The developer announcement establishes the planned demo reset and a wider launch-fix cycle, but it does not prove that every save report has been fixed in every later build. This page therefore provides diagnosis and evidence-preserving steps, not a universal file edit. Update status must remain version-aware; when the developer confirms a specific save fix, the affected section should be revised instead of preserving a launch warning indefinitely.
Sources
- KOTAMON Steam Community Hub and developer announcements — Developer statements on demo migration, launch fixes, achievements, and ongoing bug work.Checked 2026-08-26
- Steam discussion — Can't Save the Game — Multiple launch-day reports of an inaccessible layered save menu, autosave concerns, and lost progress.Checked 2026-08-26
- Steam discussion — Upgrades seem to be bugged — Multiple retail reports of cards or collectibles persisting while upgrades reset.Checked 2026-08-26
- Steam discussion — SAVE doesn't work — Additional independent reports of missing upgrades and money after reloading.Checked 2026-08-26