Tags
Creators
Details
All versions
4.2.1-beta
Beta
Petting 4.2.1-beta7 months ago 90
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
- Free Roam (Wandering) Mode: Pets can now be set to roam freely without following you. This mode bypasses the "Follow/Teleport to owner" logic while still allowing the pet to defend itself and respond to your attacks (if configured).
- Mode Cycle Update: Interacting with a Stick now cycles through: Following → Sitting → Waisting → Wandering.
- Clearer Labels: Renamed the previous generic "Wandering" label to "Following" for better clarity.
- Blacklist Interaction Block: Added a check at the start of the interaction handler (OwnerRightclicksPetProcedure.java) that immediately stops Petting from processing any action on blacklisted mobs. This ensures that even if you own a "Hybrid Pet" (like a vanilla Wolf), Petting will completely ignore it and let the original mod's interactions work or remain vanilla.
- Implemented the Global Blacklist system, which allows you to completely disable the Petting mod for specific entities. This ensures that complex entities are entirely ignored by the mod's AI, inventory, and interaction systems.
- Bound Roam Radius Fix: The pet was snapping back to its bound spot prematurely because of a hardcoded 20-block limit (400.0 squared).
- Improved the boss bar hiding logic.
- Implemented a Configurable Tool ID system that allows you to remap all of the mod's interaction items (like the Stick, Sword, or Shield) to any other item registry ID.
Full Changelog: https://github.com/yigit-guven/Petting/compare/4.2.0...4.2.1-beta
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:vf91JXwf:ByvDVyli"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vf91JXwf:ByvDVyli"
}

