Links
Tags
Creators
Details
1.0.0
Compatibility
Changes
AposaBackup v1.0.0 for Minecraft 26.2
Downloads
| File | Size |
|---|---|
AposaBackup-26.2-1.0.0.jar |
4.1 MB |
Requirements
- Minecraft 26.2
- Fabric Loader >= 0.19.3
- Fabric API 0.152.2+26.2
- Java 25+
What's New
Ported to Minecraft 26.2
- All features from the 26.1.2 branch fully ported
- Verified with clean world generation and backup/restore cycle
Core Backup System
- Scheduled automatic backups with configurable interval (default: 60 min)
- Manual backups via
/backup createwith optional comments - Automatic shutdown backup on server stop
- Local backup with ZIP compression and configurable level (1-9)
- Two-step restore with confirmation flow (
/backup restore→/backup confirm) - Pre-restore auto-backup before overwriting world data
Cloud Backup (Cloudflare R2)
- Differential upload via S3 API — only changed
.mcaregion files are uploaded - Content-addressable storage with SHA-256 deduplication
- Manifest-based backup indexing
- Garbage collection for orphaned chunks
- Custom S3 endpoint support for MinIO and compatible services
/backup downloadto export cloud backup as local ZIP
C2ME Compatibility
- C2ME compatibility layer built in (reflection-based flush)
- Awaiting C2ME release for MC 26.2 — architecture ready for immediate support once available
Single-Player Support
- Works in both dedicated servers and single-player/LAN worlds
Command System
- 14 commands under
/backupwith Brigadier registration - Tab completion for
restore,delete,info,downloadcommands - 17 hot-configurable settings via
/backup config
Retention Policy
- Local: recent N backups + daily snapshots (configurable days)
- Cloud: manifest retention + daily snapshots + garbage collection
Configuration
Default config generated at config/aposabackup.json. All options changeable via /backup config at runtime.
Known Issues
- C2ME not yet available for MC 26.2 — compatibility layer is ready but untested until C2ME updates
Changelog
- Port from Minecraft 26.1.2 to 26.2
- All 26.1.2 features carried over
Full Changelog: https://github.com/Star1ight08/AposaBackup/compare/v1.0.0-26.1.2...v1.0.0-26.2
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:MDwS9QUo:2IOjuMEP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MDwS9QUo:2IOjuMEP"
}

