1.7.5+1.21.11
Compatibility
Required content
Changes
Fixed a crash that could happen when sneak-right-clicking a collar to open the dye menu. Added a new consent option that lets the signer decide whether a collar can be forcibly equipped. If this permission is enabled, an owner can now sneak-right-click their assigned pet to equip the collar. Signing an ownership deed now requires choosing Can leash forcibly: On or Off before it can be completed. Signed ownership deeds now display Can leash forcibly: Yes/No in their tooltip.
- Added a new operator-only command:
/collar <player_to_give> <player_who_will_own> <owned_player> <true|false> Existing collars and ownership deeds will have forced equipping disabled by default to preserve previous behavior. Added additional server-side validation and several compatibility improvements for Minecraft 1.21.11.
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:vgTyt0Ay:q9pXIPct"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vgTyt0Ay:q9pXIPct"
}

