A small fan tool, shaped by real save problems
I made this editor as a fellow Silksong player. I was genuinely surprised when people began using it to recover runs and troubleshoot odd save states, so the project grew from a JSON utility into a clearer, backup-first set of player tools.
September 11, 2026
Steel Soul-first homepage and permanent help pages
Redesigned the first viewport so the editor’s clearest difference is visible immediately: verified Steel Soul recovery beside the save-file path and upload flow, followed by save-aware troubleshooting tools.
- Put the verified recovery path and its safety boundary before general resource editing.
- Kept the copyable save-folder path and upload action together in the first viewport.
- Added permanent FAQ and Updates pages with visible, prerendered content.
- Strengthened the original-backup state before recovery and final download.
September 8, 2026
Portuguese (Brazil) access
Added a Brazilian Portuguese homepage, save-location experience, and Steel Soul recovery guide so more players can find the right file and understand the safety steps before editing.
- Localized the upload, path-copy, backup, and main editing flow.
- Added Portuguese metadata and hreflang links for the localized routes.
- Kept the same local browser processing and exact Steel Soul safety rule.
August 18, 2026
V2: save-aware tools and safer editing
V2 reorganized the editor around player problems: familiar Quick Edit fields, save-aware Popular Actions, searchable Advanced Mode, and an explicit original backup before the final download.
- Added verified defeated Steel Soul detection and recovery.
- Added checker-only Plasmium Phial and Tool Pouch diagnostics.
- Added case-insensitive Advanced Search with match count and navigation.
- Added original backup downloads, clearer upload errors, and save-location paths.
- Added community guides, creator pages, accessibility work, analytics, metadata, and prerendered routes.
How release notes are written
Entries describe changes that actually shipped; experiments and local drafts are not presented as releases. A community report can explain why a checker or guide exists, but it does not become an official game schema or a guaranteed fix. When a patch changes the evidence, the relevant guide should be reviewed before the editor offers a stronger action.
Official game context
Team Cherry: Silksong Help and save recovery notes Team Cherry: Silksong Patch 2Follow the current capabilities
The FAQ explains the current safety limits. The Community Fixes hub shows which actions are verified, which remain checkers, and which reports still need better evidence.
View the public project page