Tags
Creators
Details
Licensed ARR
Published 4 months ago
Updated last week
All versions
1.2.0
Release
Lodged 1.2.04 months ago 51
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
New
- Added configurable leg-shot Slowness
- Players hit in the legs by arrows can now receive Slowness
- Added new config options for leg-shot Slowness
- Enable or disable leg-shot Slowness
- Adjust how long the Slowness effect lasts
- Adjust the Slowness level
- Added data-driven blood colors
- Mobs can now have custom blood colors through JSON files
- Blood colours support entity IDs and entity type tags
- Added default purple blood for endermen, endermites, shulkers, and the Ender Dragon
- Added default green blood for spiders and cave spiders
- Added default teal blood for wardens
- Added Simple Blood compatibility
- Lodged blood drops can now spawn matching Simple Blood ground decals when Simple Blood is installed
- Simple Blood decals use the same data-driven blood color as Lodged particles
Updated
- Improved blood particle configuration
- Lodged blood particles can now be disabled globally
- The setting applies to in-world bleeding, bleeding bursts, and inventory blood visuals
- Simple Blood compat decals can be disabled separately from Lodged blood particles
- Added config options for Simple Blood decal chance and scale tuning
- Improved blood particle tinting
- Blood particle textures now tint more cleanly
- Default blood colors were brightened for better visibility
- Updated bleeding immunity defaults
- Skeletons no longer bleed by default
- Golems, slimes, magma cubes, blazes, breezes, guardians, skeletons, and armour stands are bleeding-immune by default
- Bleeding immunity remains configurable through the
lodged:bleeding_immuneentity type tag
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:mlaUPhrZ:YR2ih90S"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mlaUPhrZ:YR2ih90S"
}

