Tags
Creators
Details
3.0.0
Compatibility
Changes
Updating from PotatoSack 2.x.x to 3.0.0
Simply replace the existing PotatoSack-2.0.0.jar with the newly released PotatoSack-3.0.0.jar. The plugin will automatically migrate the configuration files.
PotatoSack 3.0.0 introduces a new storage format for backup record files, changing from
_xxx.jsonfiles to compressed binary_xxx.binfiles. It is recommended to editplugins/PotatoSack/data/backup.jsonin the server dir and setlast_full_backup_timeto0. This will trigger a full backup immediately after the server restarts, creating a new backup group using the PotatoSack 3.0.0 format.
Alternatively, you can remove all backup groups created by PotatoSack 2.x.x from your cloud storage (or move them somewhere else) and delete the localplugins/PotatoSack/data/directory. The next full backup will then create a new backup group using the PotatoSack 3.0.0 format.
You can also choose to do nothing. When PotatoSack 3.0.0 inherits an existing backup group created by 2.x.x, the next incremental backup may produce an incremental backup archive nearly the size of a full backup. Everything will return to normal after the next full backup. (✧≖‿ゝ≖)
What's Changed
- Added support for S3 / S3-compatible object storage services;
- Introduced a custom PSMCA format for
.mcafiles in incremental backups (see the README-Concepts for details), allowing chunk level changes to be tracked. In previous versions, even a small change would cause the entire.mcafile to be backed up. This significantly reduces the size of incremental backup archives; - Fixed an issue with OneDrive and Dropbox uploads where excessive byte-array copying or recursive retries could cause object references to remain unreleased for too long, resulting in a noticeable temporary increase in memory usage during backups;
- Fixed the plugin initialization logic. If initialization fails due to an issue with
config.yml, the plugin will no longer disable itself immediately. Instead, users can fix the configuration and reinitialize the plugin using/potatosack reload; - Increased OkHttp's
CALL_TIMEOUTto prevent chunked uploads to OneDrive and Dropbox from timing out when the upload speed is too slow.
Plus a few other minor bug fixes... (´꒳`)b
Version Support
PotatoSack still supports Minecraft JE 1.19+ and Java 17+.
Backup Merging Tool
- Note: Backup groups created by PotatoSack 3.0.0 must be merged using
BackupsMerger 1.1.0or later.
Download it here: BackupsMerger 1.1.0
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:x8tNcDMW:3fDPA0iy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:x8tNcDMW:3fDPA0iy"
}

