GameSave Manager

Appears to be a malformed entry in the database.
A new Database Update will be made in the next day or two, which should address this.

Sorry about that.

I'm afraid GameSave Manager cannot detect when a USB device is plugged in. Instead, your backup will be attempted at your scheduled time and fail . GameSave Manager itself cannot help you much here without third party help. Potentially, you could have another tool execute at your scheduled time. Thi...

Thanks,
Database Update released.

Can you confirm the backup includes your saves?
Some games use different save locations for each 'release type'. For example, Steam releases often use Steam specific locations (Steam Cloud for instance) while a GoG release might use a folder in your AppData or Documents folder(s).

I wish you'd consider looking into this without automatically writing off the question with a flippant response. What do you think? I am in no way writing the issue off. If I can replicate the issue (or someone else can) regularly enough to track a cause, I will address it. With that in mind, would...

To cut a long story short, p1r473 sent me the archive through Discord.
We came to the conclusion that the file NTSTORY~1.SC2 is the cause. It's use of a 8.3 filename is causing Windows (or possibly GameSave Manager; we never fully ran the issue down) to not correctly process the file correctly.

Thanks,
Database Update released.

Thanks,
Database Update released.

Thanks,
Database Update released.

TylerC wrote: ↑15 Nov 2019, 03:40 The Celeste game was the the one the Epic store gitfted like a month ago. There are 2 files in the folder C:\Program Files\Epic Games\Celeste\Saves

Do you have a registry value I can use to dynamically detect this path?