1.2.0+26.3
Compatibility
Required content
Changes
Changelog
1.2.0
Now also available for Minecraft 26.2 and 1.21.11, built from the same source.
Fixes:
- Restoring a player who is on the death screen is now refused. Before, the restore reported success, but the respawned player came back with an empty inventory (only the ender chest survived).
- Auto-snapshots now count game time. Before, they followed the time of day, so they never happened with the daylight cycle turned off, and
/time setor sleeping could trigger extra ones. - A totem of undying saving a player no longer creates a
[death]snapshot. Before, every totem pop counted as a death and could push real death snapshots out. - Snapshots record the Minecraft data version they were saved with, and older item data is upgraded on load. Before, an item whose format changed in a Minecraft update could come back wrong (for example a stack of 64 restored as 1) with no warning.
- Items that can't be loaded (for example from a removed mod) are counted and reported by preview and restore, and listed in the server log. Before, they were skipped silently.
- Snapshot files are written to a temporary file first and then moved into place, so a crash or full disk can't leave a half-written snapshot.
Format: worn items are now saved by slot name. Snapshots from older versions still load. A snapshot saved by 1.2.0 restored with an older version of the mod would come back without its armor and offhand.
1.1.0
- Death snapshots (on by default, separate limit)
/vault preview, offline/vault listand preview, clickable Preview/Restore buttons- Partial restore:
inventory,enderchestorequipment - Safety copy before every restore:
/vault restore <player> safetyundoes it /vault settings,/vault set,/vault reset- Public API (
VaultInventoryApi,VaultInventoryEvents)
1.0.0
- First release:
/vault snapshot,list,restore, daily auto-snapshots
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:L8JAsBfC:5ar3a5IH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:L8JAsBfC:5ar3a5IH"
}
