Tags
Creators
Details
Licensed MIT
Published 8 months ago
Updated 4 days ago
All versions
0.8.6-26.3-Fabric
Release
Pets Mod 0.8.6 for Fabric 26.34 days ago 133
Uploaded by
Compatibility
Minecraft: Java Edition
26.3
Platforms
Fabric
Quilt
Supported environments
Client-side
Required content
Any compatible version
Changes
Major Changes & Updates
- Deprecation of the /petspecies, /petname, etc, commands
- These commands are now deprecated and will be removed soon. Instead, use /pet species, /pet name, etc.
- Pets Mod now has an ‘auto’ updater. It will now notify you when new updates come out, and give you the option to automatically install the new version, view it on Modrinth, or dismiss this version. You can turn off these messages in the config screen -> other -> Receive Update Notifications?
- There is a new addon API! Creating addons is now significantly easier. You still have to register the pets/renderers/etc yourself, but it is about ~2 lines of code to register a custom pet, versus the dozens from before.
- Added a new Pets sound category, so you can adjust pet volumes as you like.
Changes
- Change the sitting default setting to be off, since it gets quite confusing when your pet - just stops moving.
- Added a wandering boolean to the GeneralPetsPayload so that pets will wander based on whether the owner wants them to wander, not the person on the client
- Switched to ClassTweaker v2 as opposed to AccessWidener v2
- Made all Access Widener stuff transitive
- Added tooltips to the buttons in the Pets Config Screen
Bug Fixes
- Sounds now work on the Java Agent version
- Fixed the Java Agent version not letting you connect to servers
- Fixed the Java Agent version having commands that don’t work on servers
Supplementary resources
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:WwqTyEtB:IgYebx3Y"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WwqTyEtB:IgYebx3Y"
}

