What these Silksong save tools actually do
The three tools on this page do not behave like a list of permanent cheat codes. They inspect the uploaded userX.dat, compare the detected state with evidence verified in this project, and then choose one of three outcomes: offer a narrow recovery, explain a version-aware troubleshooting path, or remain a read-only checker.
That difference is intentional. A community post can reveal a real symptom and a useful field name, but it cannot prove that the same edit is safe for every save slot and game build. Start with the problem you can reproduce, preserve the original file, and use the result as evidence rather than a promise that every progression bug can be repaired.
Choose the problem that matches your save
These are not generic cheat buttons. Each guide begins with a player-facing symptom, shows what the editor can actually detect, and separates verified behavior from a version-dependent community workaround.
Recover a Defeated Silksong Steel Soul Save
Detect the defeated state, keep an original backup, review the one-field recovery, and test the result safely.
Recover a Defeated Silksong Steel Soul Save: step-by-step guideSilksong Plasmium Phial Save Troubleshooter
Work through game version, Shell Shards, normal recovery, and recognized save fields before editing.
Silksong Plasmium Phial Save Troubleshooter: step-by-step guideMissing a Silksong Tool Pouch Upgrade?
Check the recorded count and known flags before changing progression data.
Missing a Silksong Tool Pouch Upgrade: step-by-step guideMore save recovery and troubleshooting guides
Start with the symptom you actually see. Each guide separates official recovery steps from community-reported fallbacks and keeps backup safety visible.
Recover a Deleted or Missing Save
Try official Auto Saves first, then inspect preserved backup copies safely.
Recover a Deleted or Missing Save: open guideFix “Save Could Not Be Written”
Check storage and folder access before assuming the save data is broken.
Fix “Save Could Not Be Written”: open guideResolve “Version Incompatible”
Match the game build instead of forcing unsafe save-field changes.
Resolve “Version Incompatible”: open guideStop Progress From Resetting
Separate write failures, cloud conflicts, wrong folders, and mods.
Stop Progress From Resetting: open guideTransfer a Save Between PCs
Move userX.dat into the correct account folder without losing either copy.
Transfer a Save Between PCs: open guideBack Up a Save Safely
Keep the untouched original, working copy, and edited result separate.
Back Up a Save Safely: open guideRecovery, troubleshooter, and checker are different safety levels
The editor recognizes an exact state and the complete targeted change is known. Steel Soul recovery is enabled only for the defeated value the current implementation verifies.
An official patch and multiple community causes can produce a similar symptom. Plasmium checks the version and related values before suggesting the safest next step.
The save contains useful evidence, but not every required progression flag is verified. Tool Pouch reports the count and known flags without inventing a restore action.
How a community report becomes a save tool
- Start with a repeatable symptom. A player describes what appears in the game, not only a field they believe should be changed.
- Find the relevant save evidence. The project checks the decoded structure, field path, data type, and current value.
- Compare official changes. Patch notes and the reported game version can make an old workaround unnecessary or inappropriate.
- Define the complete mutation. A one-click action is added only when all values required for that outcome are understood.
- Keep the decision reversible. The original backup is downloaded before the edited file is generated and tested.
If one of those steps is missing, the public tool remains diagnostic. That can feel less dramatic than a “Fix Now” button, but it protects players from a confident-looking edit that changes the wrong quest or reward state.
The evidence hierarchy used by this project
1. Official game behavior and patch notes
Team Cherry help and patch notes take priority when they address the same symptom. The Plasmium guide, for example, checks the official Patch 2 bench restoration fix before treating a release-era field workaround as current.
2. Reproducible save structure
A field must exist at a stable path with the expected type and meaning. The repository fixture and the actual uploaded save are stronger evidence than a screenshot of one player's inventory.
3. Community case reports
Reddit and Steam threads show how players encountered, investigated, and sometimes resolved a problem. They help identify candidate values and failure modes, but a reply that says “worked for me” remains version-dependent until the full state transition is verified.
A backup-first diagnostic workflow
- Close Silksong and identify the affected
userX.datslot. - Copy the original outside the save folder or use Download Original Backup.
- Try an official update, normal in-game recovery, or Auto Save when relevant.
- Upload the unchanged file and open the Popular Action matching the symptom.
- Read the plain-language result before expanding technical fields.
- Make a change only when the action explains exactly what will be modified.
- Download, test once, save normally, and launch again before deleting any backup.
Test one hypothesis at a time. If Rosaries, inventory, map state, or unrelated progression changes unexpectedly, restore the untouched file and stop stacking edits onto the same download.
Keep these details with your checker result
- The installed game version and platform.
- The numbered save slot and whether an earlier Auto Save behaves differently.
- The exact in-game symptom and the steps that reproduce it.
- The field paths and values shown in technical details.
- Which official updates or normal recovery steps were already tested.
This information can support a useful bug report without publishing the entire save. Do not upload a private save to a public forum simply because a checker returns “unknown.” Start with sanitized field paths and the reproducible game behavior.
How community evidence is used
A Reddit or Steam report can prove that a player encountered a problem. It cannot prove that one field edit is safe for every game version. The editor only automates a change when the save state and complete edit are verified.
Community save fixes FAQ
Why does Steel Soul have a recovery button but Tool Pouch does not?
Steel Soul recovery has a narrowly recognized defeated state and a verified one-field transition. Tool Pouch currently has only part of the acquisition flag set, so changing the visible count could leave progression inconsistent.
Does Check My Save modify the uploaded file?
No. The checkers read the locally decoded data and display a result. A file is changed only after a separate edit is confirmed and a new download is generated.
Why can a workaround stop working after a patch?
A patch can fix the original bug, add fields, rename data, or change the relationship between values. Always compare the report date and game build with the version that wrote your save.
Can Advanced Mode force a checker-only result?
Advanced Mode exposes the values, but access is not the same as verification. If the checker says required flags are unknown, manually maximizing counters can hide the symptom without restoring the underlying reward state.