Links
Tags
Creators
Details
1.17.3
Compatibility
Changes
Fix: Skins are now yours, not the pet's
Unlocked cosmetic variants are now collected per player (per pet type) instead of being stored on the individual owned pet.
- Scrapping a pet's skin unlocks it for you regardless of whether you own that pet, and it stays in your collection even if you later scrap all your copies.
- The Customize menu and skin-swapping read from your personal collection.
- Existing data migrates automatically β your pets' current skins and previously unlocked variants are moved into your per-player collection on first load.
Compiles clean on Paper 26.2; 63/63 tests pass. Drop BetterPets-1.17.3.jar into your plugins/ folder.
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:iudkOrvv:3WYnzg1p"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iudkOrvv:3WYnzg1p"
}

