PotatoSack

After nearly seven months of development, the more robust PotatoSack 2.0.0 is finally here!

Note: Breaking Changes

PotatoSack 2.0.0 introduces significant changes compared with the 1.x.x releases. If you are currently using PotatoSack 1.x.x, we recommend that you do the following before upgrading to 2.0.0:

1. Back up your existing backup data.
2. Delete the old plugin and configuration files, then configure PotatoSack 2.0.0 from scratch.

What's Changed

1. Reorganized the codebase with a more friendly module structure and reduced coupling.
2. Rewritten the logic for toggling automatic world saving.
3. Backup schedules now use more controllable UNIX Cron expressions.
4. Introduced exponential backoff for failed backup uploads and Access Token refresh failures.
5. Added an option to pause full backups when no players are online. The logic for determining whether no player is online has also been improved, and backups will no longer start immediately after a player joins.
6. Improved the backoff logic used while waiting for asynchronous saves to finish before starting streaming compression and upload.
7. Added support for configuring the base directory (baseDir) used to store backups in the cloud.
8. Added Dropbox support (#1 @Sunakier).
9. Added a version number to the configuration file. In addition, backup configurations now specify paths to back up instead of world names.
10. Added support for specifying files and directories to exclude from backups using a .potatosackignore file located in the server root directory. See the README for details.
11. Fixed several issues that caused excessive log output.
12. /potatosack reload can now properly reload the configuration without restarting the server.

Along with various other bug fixes...

Version Support

PotatoSack still supports Minecraft Java Edition 1.19 and later.

BackupsMerger

Download it here: BackupsMerger