Tags
Creators
Details
Licensed ARR
Published 4 months ago
Updated 2 weeks ago
All versions
1.4.1
Release
Tame Every Mob 1.4.1 - Fabric 1.21.13 weeks ago 130
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Changes
Tame Every Mob 1.4.1
Fabric · Minecraft 1.21.1 · Java 21
Added and improved
- Added colored Sun Shield upgrades for all 16 vanilla wool colors, crafted with three matching wool and two sticks.
- Added per-pet Attack Players and Attack other Tamed Mobs settings. Both are off by default; owners and their own pets remain protected.
- Added Extra Room I–V, Range Pocket I–III, and Healing Pocket upgrades.
- Added species-specific taming hearts for cows, pigs, zombies, skeletons, and sheep. More species will receive their own hearts in future updates.
- Added a colored Pocket collection beam with a clearer route for distant items.
- Improved command search for Tame Every Mob items and enchantments.
- Added compact upgrade and Pocket descriptions; hold Shift for more details.
- Ability key labels now show the configured key, and slime riding uses jump input.
Pocket changes
- Pocket display names now use Leather, Iron, Gold, Diamond, and Netherite; existing IDs remain compatible.
- Pockets preserve complete mob data, and the owner lock prevents releasing another player's stored pet.
- Failed releases keep the stored pet data intact. Physically destroying a dropped filled Pocket releases its pets.
- Pocket tier upgrades preserve stored pets and enchantments.
- Pocket enchantments are currently available in Creative; Survival availability is planned for a future update.
Fixes
- Fixed an issue that could prevent the Guide Book from opening.
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:RguUDsjE:kIvdliM4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RguUDsjE:kIvdliM4"
}

