Tags
Creators
Details
1.0.0
Compatibility
Changes
DataGuard — Version Changelog
v1.0.0 — Initial Release
April 18, 2026
🎉 First Public Release
Automatic Saving
- Players are automatically snapshotted on join
- Players are automatically snapshotted on quit
- Server-wide auto-save runs every 30 minutes (configurable)
- Per-player auto-save toggle via
/data automatic <true/false> - Server-wide auto-save toggle via
/data server automatic <true/false>
Player Data Snapshots
- Saves inventory, armor, offhand, ender chest, XP, health, hunger, potion effects, location, and game mode
- Players can manually create and delete their own snapshots
- Admins can create, delete, and load snapshots for any player
Server Data Snapshots
- Captures all online players in a single snapshot
- Stores server metadata including world time and online player count
- Admins can create, delete, and load full server snapshots
Commands
/data player create [label]/data player delete <label>/data server create [label]/data server delete <label>/data server automatic <true/false>/data automatic <true/false>/data load player <player> <snapshot>/data load server <snapshot>/data list player [name]/data list server/data reload
Anti-Abuse
/data loadis restricted to admins only to prevent item duplication exploits
Configuration
- Configurable auto-save interval
- Configurable max snapshots per player and server
- Fully customizable messages and chat prefix in
config.yml
Permissions
dataguard.admin— Full access to all commands (default: OP)dataguard.player— Access to member-level commands (default: true)
Compatibility
- PaperMC 1.21.11
- Java 21+
- Zero external dependencies
Future versions may include: GUI snapshot browser, per-world snapshot support, Discord webhook notifications, and offline player snapshot loading.
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:nKuiAttI:4MDfK8y5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nKuiAttI:4MDfK8y5"
}

