Game Save Utility 是一个轻量的 Windows 桌面应用，用于手动管理任意单机游戏的本地存档备份与恢复。
项目使用 Rust + eframe/egui 开发，目标是生成尽量独立的单个 exe 文件。运行应用不需要安装 Node、Python、Java、Electron 或 .NET Runtime。
0.1.2 是一个维护与稳定性增强版本，重点改进备份安全、配置恢复、错误提示本地化和 Windows 发布验证。
本版本不包含重大新功能，主要修复和优化自动备份清理、增量备份恢复校验、配置备份恢复、应用数据标识迁移、中英文错误提示一致性等问题。
本项目定位为 Windows 单平台工具。新应用数据目录为 %LOCALAPPDATA%\GameSaveUtility；旧 GameSaveBackupTool 数据目录和位置文件仍会兼容识别，并在安全条件满足时迁移。
- 多游戏配置管理
- 手动添加、编辑、删除游戏
- 文件夹选择对话框
- 存档目录递归备份
- 默认使用增量备份，重复内容通过共享对象库复用
- 可为单个游戏选择 ZIP 压缩备份
- 备份标签和自动时间戳
- 每个备份节点写入
metadata.json - 按游戏分目录管理备份
- 备份历史列表按时间倒序展示
- 恢复前自动创建“恢复前自动备份”
- 备份历史支持单选恢复、全选/多选删除，删除前确认
- 删除游戏配置时可选择是否同时删除备份文件
- 常见游戏路径预设
- 扫描 Steam 库，识别已安装游戏并提供候选存档目录
- Steam 扫描结果使用独立窗口，左侧游戏列表可拖动右边缘调整宽度
- 对 Steam Cloud 本地缓存和本地存档修改时间差异给出冲突提醒
- 每个游戏可设置最大备份数量和自动清理
- 每个游戏可设置定时自动备份和存档变更提醒，间隔支持分钟/小时单位切换
- 支持快捷键：
Ctrl+S快速备份，Ctrl+R恢复选中备份，方向键导航列表 - 打开存档目录、打开备份目录
- 首次关闭时可选择“最小化到系统托盘”或“直接退出软件”
- 支持系统托盘图标，双击恢复窗口，右键菜单可显示窗口或正常退出
- 自动记住主窗口大小和最大化状态
- 支持更改
GameSaveUtility数据目录，并迁移旧目录内容 - 支持中文 / English 双语界面，顶部按钮可切换并持久保存
- 顶部提供“使用文档 / Docs”按钮，打开可拖出主窗口的独立帮助窗口，支持目录和搜索
- 内置应用图标，并嵌入到 release exe
- 中文状态提示和简单日志记录
- Boss 战前保存一个安全备份
- 剧情关键选择前保存进度
- DLC、二周目或不同流派开局前保存节点
- 防止误删、覆盖或云存档同步异常
- 管理多个单机游戏的本地存档
- 启动应用。
- 点击“添加游戏”。
- 输入游戏名称。
- 选择或填写游戏存档目录。
- 按需设置最大备份数量和自动清理。
- 在主界面输入备份标签，点击“立即备份”。
- 在备份历史中勾选备份后，可以单选恢复或多选删除；“全选备份”只用于删除选择，不会触发备份或批量恢复。
恢复存档前，应用会先自动备份当前存档目录，标签为“恢复前自动备份”。
也可以点击左侧“扫描Steam库”，从已安装的 Steam 游戏中批量添加有候选存档路径的游戏。扫描结果窗口中，左侧游戏列表的右边缘可以拖动，用于调整列表宽度。
定时自动备份的间隔使用整数输入，并可在“分钟 / 小时”之间切换单位。例如要测试半小时自动备份，可以选择“30 分钟”。
主界面顶部的“English / 中文”按钮可切换界面语言；“使用文档 / Docs”会打开独立帮助窗口。帮助窗口随当前语言显示对应内容，并提供目录和搜索，可以拖到主窗口外侧，方便边看文档边操作工具。
应用会自动在当前 Windows 用户的应用数据目录下创建配置、日志和默认备份目录：
%LOCALAPPDATA%/GameSaveUtility/
config.json
logs/
app.log
backups/
配置文件为 JSON，便于查看、迁移和排查问题。主界面顶部提供“数据目录 -> 更改并迁移”。选择新位置后，应用会迁移配置、日志和默认备份目录，并写入位置文件：
%LOCALAPPDATA%/GameSaveUtility.location.json
首次运行新版时，如果新目录不存在而旧目录
%LOCALAPPDATA%/GameSaveBackupTool/ 存在，应用会将旧目录迁移为新目录，并保留配置与备份。
backup_root/
GameA/
.objects/
6c/
6c6e714a...
2026-06-13_21-30-15_关键选择前/
metadata.json
manifest.json
2026-06-14_00-12-45_ZIP示例/
metadata.json
save_files.zip
v0.1.1 起，新备份默认使用增量布局：每个备份节点包含 metadata.json 和 manifest.json，游戏备份目录下的 .objects/ 共享对象库保存实际文件内容。首次增量备份会把当前所有文件内容写入对象库，备份历史类型显示为“全量”；后续备份只为新增或变化的内容写入新对象，类型显示为“增量”。每个备份节点仍然代表一个完整快照，恢复时会按 manifest 重建完整存档目录。增量备份节点不会创建 save_files/ 目录，这是预期行为。更换备份根目录本身不会自动创建备份；在新的空目录里下一次手动备份会成为该目录下的首次完整快照。
如果某个游戏选择 ZIP 备份格式，备份节点会包含 metadata.json 和 save_files.zip。ZIP 是压缩后的完整快照，恢复时会先解压到临时目录，再执行安全恢复流程。
v0.1.0 及更早版本的完整复制备份仍然兼容：包含 save_files/ 的旧备份节点可以继续扫描、恢复和删除。
备份时：
- 不修改原始存档目录
- 先写入临时备份目录
- 元数据写入完成后再提交为正式备份目录
- 备份失败时清理未完成的临时目录
- 阻止把备份根目录设置到存档目录内部，避免递归备份
恢复时：
- 先检查备份节点和对应存储内容
- 目标存档目录不存在时尝试创建
- 恢复前一定创建“恢复前自动备份”
- 使用临时目录分阶段恢复
- 恢复失败时保留恢复前自动备份，并显示错误提示
Steam Cloud 冲突提醒只基于本机文件时间的启发式检测。应用不会访问 Steam 网络 API，不会读取账号、密码、Cookie 或登录状态；检测到差异时只提示风险，不会阻止备份或恢复。
开发和编译需要：
- Windows
- Rust stable 工具链
- Cargo
建议使用 MSVC 目标：
x86_64-pc-windows-msvc
cargo runcargo test当前包含多项单元测试，覆盖备份、恢复、删除、Steam 库扫描、运行时图标加载和数据目录迁移等关键行为。
开发时可以直接构建：
cargo build --release正式发布建议使用脚本，脚本会在私有构建目录中编译，并只把面向用户的正式文件放入 release 目录：
.\scripts\build-release.ps1生成文件示例：
target/release/Game_Save_Utility_V0.1.2.exe
脚本会按 Cargo.toml 中的版本号生成文件名。发布构建已启用 LTO、单代码生成单元和 strip。
- 项目正式名称和用户可见名称统一为
Game Save Utility。 - 正式发布文件名必须带版本号，例如
Game_Save_Utility_V0.1.2.exe。 - Cargo 内部包名为
game-save-utility。 - 不要再使用旧名称
game-save-backup-tool作为项目名或发布文件名。
src/
main.rs 应用入口
app.rs GUI 状态和主要交互
archive.rs ZIP 备份创建和恢复
models.rs 核心数据结构和错误类型
config.rs JSON 配置读写
backup.rs 备份、恢复、扫描、删除、自动清理
cloud.rs Steam Cloud 本地缓存冲突检测
help.rs 内置帮助内容
i18n.rs 双语界面文本
presets.rs 内置游戏预设
scheduler.rs 定时自动备份和变更提醒判定
snapshot.rs 增量备份清单和共享对象库
steam.rs Steam 库扫描和候选存档目录识别
tray.rs Windows 系统托盘
fs_utils.rs 文件系统工具、路径展开、目录统计、复制
logger.rs 简单日志
ui/
backup_list.rs 右侧信息区和备份列表
dialogs.rs 弹窗、Steam 扫描结果窗口和帮助窗口
game_list.rs 左侧游戏列表
assets/
app.ico
app-icon-256.png
readme-icon.png
scripts/
build-release.ps1
- 备份或恢复前请关闭对应游戏，避免存档文件被占用。
- 预设路径只是候选值，实际存档位置以本机环境为准。
- 删除游戏配置默认不会删除已有备份。
- 恢复操作会替换目标存档目录内容，请确认选择了正确的备份节点。
- “全选备份”只用于删除选择；恢复操作始终只对单个选中备份生效。
- 更改数据目录前，建议确认没有正在备份或恢复。
- 大型存档目录复制可能需要等待，当前版本暂未显示复制进度。
- 备份和恢复后台任务
- 大文件复制进度条
- Steam 扫描后台化
- 自动备份目录扫描节流，减少主线程 hash 开销
- 导入、导出配置
- 搜索游戏
- 更完整的测试覆盖
- 安装包
Game Save Utility is a lightweight Windows desktop app for manually backing up and restoring local save files for single-player games.
The app is built with Rust + eframe/egui and is designed to ship as a mostly self-contained exe. Users do not need Node, Python, Java, Electron, or the .NET Runtime to run it.
Version 0.1.2 is a maintenance and stability release focused on backup safety, configuration recovery, localization consistency, and Windows release verification.
This version does not introduce major new user-facing features. It improves automatic backup cleanup, incremental backup restore validation, configuration backup recovery, app data identifier migration, and Chinese/English user-facing messages.
Game Save Utility remains a Windows-only tool. The new application data directory is %LOCALAPPDATA%\GameSaveUtility; legacy GameSaveBackupTool data directories and location files remain supported and are migrated when it is safe to do so.
- Manage multiple game profiles
- Add, edit, and delete games manually
- Pick folders through a native folder dialog
- Recursively back up save folders
- Use incremental backups by default and reuse duplicate content through a shared object store
- Optionally choose ZIP-compressed backups per game
- Add backup labels and automatic timestamps
- Write
metadata.jsonfor every backup node - Store backups by game folder
- Show backup history in reverse chronological order
- Automatically create a pre-restore backup before restoring
- Restore one selected backup, select all or multiple backups for deletion, and confirm before deleting
- Optionally remove backup files when deleting a game profile
- Built-in common save path presets
- Scan Steam libraries, detect installed games, and suggest candidate save folders
- Open Steam scan results in a separate window with a resizable game list
- Warn when Steam Cloud local cache and local save folders have different latest modified times
- Configure max backup count and automatic cleanup per game
- Configure scheduled automatic backup and save-change reminders per game, with minute/hour interval units
- Use shortcuts:
Ctrl+Sto back up,Ctrl+Rto restore the selected backup, and arrow keys to navigate lists - Open the save folder or backup folder from the UI
- Choose whether closing the window minimizes to tray or exits the app
- Restore the window from the system tray and exit through the tray menu
- Remember the main window size and maximized state
- Move the
GameSaveUtilitydata directory and migrate existing data - Switch between Chinese and English in the app, with the choice saved to config
- Open a detachable Help / Docs window with contents and search
- Embed an application icon into the release exe
- Show localized status messages and write simple logs
- Create a safe backup before a boss fight
- Save progress before major story choices
- Keep restore points for DLC, new playthroughs, or different builds
- Protect against accidental deletion, overwrite, or cloud sync issues
- Manage local save files for multiple single-player games
- Start the app.
- Click Add Game.
- Enter the game name.
- Choose or enter the game's save folder.
- Set a max backup count and automatic cleanup if needed.
- Enter a backup label on the main screen and click Back Up Now.
- Tick backups in the history list to restore one selected backup or delete multiple backups. Select All only affects delete selection; it does not start backup or batch restore.
Before restoring a save, the app automatically backs up the current save folder with the label Pre-restore automatic backup.
You can also click Scan Steam Libraries to add installed Steam games that have candidate save folders. In the scan results window, drag the right edge of the game list to resize it.
Scheduled auto backup intervals use integer input with a Minutes / Hours unit selector. For example, use 30 Minutes to test a half-hour interval.
The English / 中文 button in the top toolbar switches the UI language. The Help / Docs button opens a detachable help window that follows the current language and includes contents plus search.
The app creates config, logs, and the default backup folder under the current Windows user's app data directory:
%LOCALAPPDATA%/GameSaveUtility/
config.json
logs/
app.log
backups/
The config file is JSON, so it is easy to inspect, move, and troubleshoot. The toolbar includes a Data Directory -> Change and Migrate action. After a successful migration, the app writes a location file:
%LOCALAPPDATA%/GameSaveUtility.location.json
On the first run of the renamed version, if the new folder does not exist but
%LOCALAPPDATA%/GameSaveBackupTool/ does, the app migrates the legacy folder
to the new location while preserving configuration and backups.
backup_root/
GameA/
.objects/
6c/
6c6e714a...
2026-06-13_21-30-15_before-key-choice/
metadata.json
manifest.json
2026-06-14_00-12-45_zip-example/
metadata.json
save_files.zip
Since v0.1.1, new backups use the incremental layout by default: each backup node contains metadata.json and manifest.json, while the game backup folder's .objects/ store keeps the actual file contents. The first incremental backup stores all current file contents as objects and is shown as Full in the history list; later backups only add objects for new or changed content and are shown as Incremental. Every backup node still represents a complete snapshot, and restore rebuilds the full save folder from the manifest. Incremental backup nodes do not create a save_files/ directory; that is expected. Changing the backup root does not create a backup by itself; the next manual backup in a fresh empty root becomes that root's first full snapshot.
If a game uses ZIP backup mode, each backup node contains metadata.json and save_files.zip. ZIP backups are compressed full snapshots; restore extracts the archive to a temporary folder before running the safe restore flow.
Legacy v0.1.0 full-copy backups remain compatible. Backup nodes containing save_files/ can still be scanned, restored, and deleted.
When backing up, the app:
- Does not modify the original save folder
- Writes backup content into a temporary backup folder first
- Commits the backup only after metadata is written
- Cleans up unfinished temporary folders if backup fails
- Blocks placing the backup root inside the save folder to avoid recursive backups
When restoring, the app:
- Checks the backup node and its storage payload first
- Tries to create the target save folder if it does not exist
- Always creates a pre-restore backup before replacing files
- Uses a temporary folder for staged restore work
- Keeps the pre-restore backup if restore fails and shows an error
Steam Cloud conflict warnings are local heuristics based on file modified times. The app does not call Steam network APIs and does not read account credentials, cookies, or login state. A detected difference only warns the user; it does not block backup or restore.
- Windows
- Rust stable toolchain
- Cargo
The MSVC target is recommended:
x86_64-pc-windows-msvc
cargo runcargo testThe current test suite covers backup, restore, deletion, Steam library scanning, runtime icon loading, and data directory migration behavior.
For development builds:
cargo build --releaseFor user-facing release builds, use the script:
.\scripts\build-release.ps1Example output:
target/release/Game_Save_Utility_V0.1.2.exe
The script reads the version from Cargo.toml and creates a versioned release filename. Release builds enable LTO, a single codegen unit, and strip.
- The official project and user-facing name is
Game Save Utility. - Release exe filenames must include the version, for example
Game_Save_Utility_V0.1.2.exe. - The internal Cargo package name is
game-save-utility. - Do not use the old name
game-save-backup-toolfor the project or release files.
src/
main.rs app entry point
app.rs GUI state and main interactions
archive.rs ZIP backup creation and restore
models.rs core data structures and error types
config.rs JSON config loading and saving
backup.rs backup, restore, scan, delete, cleanup
cloud.rs Steam Cloud local-cache conflict checks
help.rs built-in help content
i18n.rs bilingual UI text
presets.rs built-in game presets
scheduler.rs scheduled auto backup and change-reminder decisions
snapshot.rs incremental backup manifests and shared object store
steam.rs Steam library scanning and save path detection
tray.rs Windows system tray integration
fs_utils.rs filesystem helpers
logger.rs simple logging
ui/
backup_list.rs right-side details and backup list
dialogs.rs dialogs, Steam scan window, help window
game_list.rs left-side game list
assets/
app.ico
app-icon-256.png
readme-icon.png
scripts/
build-release.ps1
- Close the target game before backing up or restoring, otherwise save files may be locked.
- Built-in save path presets are only candidates; the real location depends on the local machine.
- Deleting a game profile does not delete existing backups by default.
- Restore replaces the target save folder contents, so make sure the selected backup is correct.
- Select All only affects deletion selection. Restore always operates on one selected backup.
- Before changing the data directory, make sure no backup or restore operation is running.
- Large save folders may take time to copy. The current version does not show copy progress yet.
- Background backup and restore tasks
- File-copy progress reporting
- Background Steam library scanning
- Throttled automatic-backup directory hashing
- Import and export config
- Game search
- More complete test coverage
- Installer package