Tags
Creators
Details
Licensed AGPL-3.0-only
Published 3 years ago
Updated last month
All versions
21.10.5
Release
[FABRIC] [1.21.10] MutantMonsters v21.10.58 months ago 8,802
Compatibility
Minecraft: Java Edition
1.21.10
Platform
Fabric
Supported environments
Client and server
Required content
Changes
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
[v21.10.5-1.21.10] - 2025-12-26
Changed
- Creeper minions on your shoulders can no longer be seen at all to fully bypass the
Received attachment change for unknown target!issue on Fabric
[v21.10.4-1.21.10] - 2025-12-25
Changed
- Creeper minions carried on your shoulders can no longer be seen by other players in multiplayer as a workaround for
the
Received attachment change for unknown target!issue on Fabric (NeoForge remains unchanged)
[v21.10.3-1.21.10] - 2025-12-07
Changed
- Mutant endermen are no longer permitted to spawn on the main island in the End
Fixed
- Fix mutant endermen being unable to spawn on the surface in the End dimension
- Fix mutant endermen becoming stuck when dying after being reloaded
- Fix crash caused by high spawn weights set in the common config file
[v21.10.2-1.21.10] - 2025-11-17
Fixed
- Fix a desync issue where a mutant zombie would vanish on the client but still be present on the server when it is killed while already on fire like with a flame enchanted bow
- Fix mutant creeper attacks causing
NaNdelta movement when both the creeper and the target are at the exact same position in the world - Fix mutant zombies missing from the
minecraft:zombiesentity tag
[v21.10.1-1.21.10] - 2025-10-20
Fixed
- Fix
java.lang.ArithmeticExceptionwhen setting mutant spawn weight to zero
[v21.10.0-1.21.10] - 2025-10-09
Changed
- Update to Minecraft 1.21.0
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:derP0ten:9PnXn3K4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:derP0ten:9PnXn3K4"
}



