All versions
1.0.4
Release
PluralBackupJava 1.0.04 months ago 84
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
Platforms
Bukkit
Paper
Spigot
Changes
2026-06-25
Unified GitHub Backup Scheduling
- Removed standalone GitHubScheduler
- GitHub backup no longer uses a standalone scheduler, but is integrated into the main backup flow
- When interval mode or time-based mode triggers a backup, if
github.enabled: trueand properly configured, the backup is automatically uploaded to GitHub after completion /backup github-uploadcommand can still manually trigger backup + upload- Fixed the issue of "backing up every hour even when auto-backup is disabled"
Multi-Language Configuration
- Added language config to config.yml
- Supports manual language specification (e.g.
zh_CN,en_US,ja_JP) - Leave empty to auto-detect server language
- Priority: config.yml setting > auto-detect > default English
- Supports manual language specification (e.g.
Removed Hardcoded Messages
- Removed backup-start-message etc. from config.yml
- All messages are now managed by the multi-language system
Modified Files
src/main/java/cn/plural/backup/manager/GitHubScheduler.java- Deletedsrc/main/java/cn/plural/backup/manager/BackupManager.java- Integrated GitHub uploadsrc/main/java/cn/plural/backup/PluralBackup.java- Removed GitHubScheduler referencesrc/main/java/cn/plural/backup/command/BackupCommand.java- Removed GitHubScheduler parametersrc/main/java/cn/plural/backup/config/PluginConfig.java- Removed message fields, added language fieldsrc/main/java/cn/plural/backup/i18n/LanguageManager.java- Support config.yml language settingsrc/main/resources/config.yml- Added language config, removed hardcoded messages
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:NmR4YWy3:UlfeSzt0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NmR4YWy3:UlfeSzt0"
}

