Describe the bug
Since updating to 3.5, I've been getting this warning that the backup has failed. Logs appear to indicate it's getting stuck on something from Biomancy

To Reproduce

1. Seemingly just allowing a backup to trigger with Biomancy installed.

Expected behavior
Backup to complete as before

Screenshots

Versioning (please complete the following information):

• OS: Windows 11
• Minecraft Version(s): 1.20.1
• Modloader(s): Forge
• Mod Version: 3.5

Additional context
https://gist.github.com/MuteTiefling/cf1e4c6c660c242b27f8ebd1e88ace6d

Hmm, and was 3.4 able to make the backup fine with Biomancy installed?

Okay. I've been trying to reproduce this, to no avail.

With AB and Biomancy installed only, both scheduled backups and manual backups correctly hash the file and back it up.

Could I have a full modlist please?
I'm also wondering why there's no visible stacktrace, as it's meant to print one out directly after reporting the error..

Hrm, alright. Wonder if something has gotten corrupt in my world then...

Forced a crash to get a full mod list for you: https://gist.github.com/MuteTiefling/a8af94ab98785a979f06124115582361

I'd be surprised if corruption could do it... but perhaps, could you send over your AB config and the biomancy.spatial.db from the data directory?

Sure thing!

ab issue.zip

Take two!

This is being fixed in multiple ways:

• Add a blacklist for files to not backup
• Skip a file if it cannot be backed up.
• If any files were skipped, log them in the console / send to a command runner.
• In an upcoming version, toasts will also show the skipped files.