Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated last month
All versions
1.3.2-1.20.1
Release
CravenCraft's Bloody Bits 1.3.2-1.20.12 years ago 117.2K
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
V1.3.2 More Bug Fixes
- Fixed a bug causing explosive events to spray blood from gun sources such as the player. Special thanks to slava110 for this fix.
- Made the show_mob_damage client config always set to false until it is fully ready to be implemented. Should prevent any accidental server crashes if someone configures it.
- Fixed a bug that was causing server crashes (Forgot I didn't move the client events to their own client-side only class).
- Updated README to reflect recent minor version bump.
V1.3.1
- Hotfix for a potential game crashing bug with certain entities.
V1.3.0
NOTE: HIGHLY RECOMMENDED TO DELETE PREVIOUS CONFIG FILES PRIOR TO UPDATING.
- Remade all blood spatter textures to be a bit more detailed with different opacities.
- Exploding mobs such as creepers now produce huge blood sprays on explosion.
- Fixed bug that allows blood spatters to catch on fire.
- Fixed bug that causes a blood fountain whenever the player dies, but does not respawn.
- Added an option to blacklist the player (all players) from being an entity that can bleed.
- Stopped blood from triggering buttons and interacting with other entities.
- Removing blood sprays/chunks on entity death until I find a better & less crash-prone solution.
- Major rework to blood entities. They no longer extend the AbstractArrow class, which fixes the catching fire, button pressing, and some crashing bugs. As well, allowed me to remove some mixin classes that were prone to errors when using Sinytra Connector.
- Added config option to modify the blood spray radius.
- Fixed minor bug that caused blood to not spray in certain directions.
- Added an optional bleed effect (default is false. Enable in config.) when an entity is below 50% health that bleeds more as they get lower in health.
- Experimenting with a system for showing entity damage. If it viable, it will be fully implemented in the future.
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:4xxMfxFO:ypg9FsKc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4xxMfxFO:ypg9FsKc"
}

