Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated last year
All versions
6.2.1+1.21
Release
[1.21 - 1.21.1] Haemorrhage - 6.2.1last year 1,099
Uploaded by
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Changes
- moved config file to imbleeding folder
- removed 2 config options: armorBleedingProtection and toughnessBleedingProtection
- added new attribute: Bleeding Protection (works the same as armorBleedingProtection and toughnessBleedingProtection combined together, but is visible on armors)
- it is now possible to specify bleeding protection for each armor part individually (new file will appear in your config after entering and leaving world, cannot be accessed via mod menu)
- added new item tag: weapons_pierce_bleeding_protection (items from this tag ignore some bleeding protection)
- added 2 config options:
- sharpWeaponBleedProtPiercing - 0.15 means that 15% of bleeding protection will be ignored when using weapon from weapons_pierce_bleeding_protection tag
- anyWeaponBleedLengthIncrease - 0.10 means that calculated bleeding will be increased by 10% when using any damageable tool (same behaviour was before, but hardcoded, and the value was 0.17)
- (probably) fixed "Accessing legacy random source from multiple threads" crash while having particles set to decreased in video settings
- player always gets slowness for 30s when Broken expires or is removed
- honey bandage removing poison is no longer hardcoded
- herbal balm removes poison
- removed 4 item tags (items_remove_bleeding, items_remove_health_loss etc.)
- effect removal is now done via Unremovable Effects (data/unremovableeffects/items_remove_status_effects/)
- added option to disable blood particles server sided
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:lYoBWCSj:yr9PV8s9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lYoBWCSj:yr9PV8s9"
}



