Tags
Creators
Details
Licensed ARR
Published 4 months ago
Updated 23 hours ago
All versions
1.4.2
Release
Tame Every Mob 1.4.2 - NeoForge 1.21.1123 hours ago 8
Compatibility
Minecraft: Java Edition
1.21.11
Platform
NeoForge
Supported environments
Client and server
Changes
Tame Every Mob 1.4.2
Added
- Added the Patrol & Defence Station with Glowstone fuel, pet deployment, customizable patrol routes, and private route previews.
- Added the Breeding Upgrade for taming offspring.
- Added a Server Config menu for admins to manage tameable mobs, with search and category filters:
/tameeverymob config.
Changed
- Rebalanced normal-mob upgrade tasks for fairer progression.
- Taming chances now scale with game difficulty.
- Supported swords and armor now convert into Pet Upgrades when taming.
- Improved Stay behavior.
- Improved the Pocket selection HUD and pet previews.
- Renamed
/tameeverymob upgradeto/tameeverymob levelup, with owned mob-type and quantity selection. - Removed the standalone rename command. Renaming remains available through the pet menu.
Fixed
- Fixed Creeper recovery and related task progress after restarts.
- Fixed unloaded pets disappearing from the pet list and improved aquatic Recall safety.
- Fixed Slime ownership and duplicated upgrades after splitting.
- Fixed LifeStone and Best Body recovery, including inventory and upgrade preservation.
- Fixed pet regeneration when the owner is offline.
- Sun Shield now prevents sunlight ignition without extinguishing unrelated fire.
- Wild Iron Golems no longer attack tamed monsters without provocation.
- Fixed premature Last Stand activation and Fire Attack triggering on blocked hits.
- Various bug fixes and improvements.
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:va0N69Et"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RguUDsjE:va0N69Et"
}

