Links
Tags
Creators
Details
Licensed MIT
Published 3 months ago
Updated last month
All versions
1.1.9
Release
Better Mob Combat - Reimagined 1.1.93 months ago 385
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Better Mob Combat Reimagined 1.1.9
Combat
- Added attack delays for empty-handed mobs.
- Added attack delays for mobs holding shovels, hoes, pickaxes, and other non-combat items.
- Added fallback swing animations for non-combat items.
- Applied the extra attack range config to fallback melee attacks.
- Fixed custom melee mobs bypassing the configured attack delay.
- Improved compatibility with Mob AI Tweaks cooldown changes.
- Prevented dual-wielded weapons from being treated as shields.
- Cancelled delayed attacks when the held item or target becomes invalid.
Fresh Animations and EMF
- Fixed baby zombie variants changing into adult-sized models.
- Restored Better Combat swing animations for baby zombie variants.
- Fixed Vindicator attacks while swimming.
- Fixed Vindicator legs moving into or away from the body during attacks.
- Fixed the small Vindicator head bounce during attacks.
- Fixed slow and stuttering Vindicator swing animations.
- Preserved Fresh Animations movement while Better Combat controls the attack arms.
- Preserved two-handed weapon and held-item transforms with Fresh Animations.
- Fixed duplicate Illager hat rendering.
Internal
- Added a post-EMF animation overlay for Better Combat attack rotations.
- Improved baby-model scaling compatibility with Player Animator.
- Improved fallback melee range and attack validation.
Still having issues?
- Please submit bugs to the GitHub Issue Tracker!
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:ZMyutZkx:4j0309LJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZMyutZkx:4j0309LJ"
}

