All versions
v1.4.0-mc26.2
Release
Pet Vault 1.4.03 months ago 10
Compatibility
Minecraft: Java Edition
26.2
Platform
Forge
Supported environments
Client and server
Changes
[1.4.0] — 2026-08-24
Added
- Auto-riding now covers the remaining vanilla mounts: llamas, trader llamas, nautiluses, zombie nautiluses and happy ghasts are in the
pet_vault:auto_rideabletag, so shift-left-clicking a stored one summons and mounts it. Nautiluses and llamas were already storable, so this was the only piece missing; happy ghasts still need opting intostorableEntities(or thepet_vault:storabletag) first, as they have no vanilla owner
Fixed
- Unregistering a storable entity (e.g. an iron golem, or any type opted in via
storableEntities/ thepet_vault:storabletag) now returns it to unclaimed. Previously the owner marker was left behind, so the detached entity could never be stored again by anyone — including the player who released it
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:Sm1QteFy:O17uVcwd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Sm1QteFy:O17uVcwd"
}

