Tags
Creators
Details
Licensed LGPL-3.0-only
Published 4 years ago
Updated last year
All versions
1.4
Release
[Fabric] Solid Mobs 1.4 [1.19]4 years ago 118
Compatibility
Minecraft: Java Edition
1.19
Platform
Fabric
Supported environments
Client and server
Required content
Unavailable version
Changes
Solid mobs change-log
v1.4
- fixed an issue with item entities glitching around when thrown and similar problems with projectile entities
v1.3
- added ability to shove mobs out of your way without punching if you get stuck, simply right click them while crouching to give a small knock-back, has a cool-down time set by config, (less effective on villagers, longer cooldown & triggers reaction from hostile mobs)
- config option added to allow or disable villager collisions (A big part of villagers I believe is that they have a mind of their own, I do not want to encroach on this and have limited their shove-ability, as this means you can possibly get stuck the option to disable villager collisions has been added)
- set collisions to only apply to living mobs, (prevents issues with mods like Immersive portal's portal entities)
- item, item frame & painting options and collisions removed for now
- fixed hostile mobs standing on their being unable to attack them
v1.2
- dead or dying entities no longer have collisions fixing incompatibility with fast mob farms
- setting to allow invisible entity collisions (disabled by default)
- item frame and painting collisions now disabled by default
- fall damage transferred to a fallen upon entity now registers to the victim as an attack from the faller (e.g. hurting zombie-piglins in this way will trigger their hostility)
- added Allays to the pet collision exemption list in 1.19 version
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:uEXYxtEF:CxJdCYqZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uEXYxtEF:CxJdCYqZ"
}

