Tags
Creators
Details
3.8.2
Compatibility
Changes
🩸 PixelBlood v3.8.2 — Minecraft 1.26.3 Update
This update introduces mob bleeding, improved blood visuals, expanded configuration options, and Minecraft 1.26.3 compatibility updates!
✨ New Features
🩸 Mob Bleeding System
- Mobs can now suffer from bleeding after taking damage.
- Continuous bleeding particles and ground droplets.
- Configurable bleeding chance, duration, and damage intervals.
- Optional bleeding support for bosses.
- Automatic cleanup when mobs die, despawn, or unload.
- Separate configuration settings for player and mob bleeding.
🎨 Improved Blood Visuals
- Improved mob-specific blood colours and materials.
- Zombies now produce green blood using their configured profiles.
- Blood trails, combat bursts, and death effects use consistent colours.
- Added three combat particle modes:
BLOCK— Block-breaking blood fragments.DUST— Coloured particle effects.MIXED— Combines both effects.
- Removed unwanted red particle fallbacks.
⚙️ Expanded Admin GUI
- Additional configuration pages for blood effects.
- Adjustable particle settings directly in-game.
- Particle preview functionality.
- New configuration controls for mob bleeding.
- Improved menu navigation and organisation.
🔧 Bug Fixes & Improvements
- Fixed combat particle modes not applying correctly.
- Fixed certain effects ignoring configured mob blood colours.
- Improved blood trail and pool visual consistency.
- Fixed hardcoded red death effects.
- Improved particle cleanup and effect management.
- Corrected configuration formatting.
- Improved compatibility between existing blood systems.
✅ Compatibility
- Updated for Minecraft 1.26.3.
- Existing player bleeding and blood effects retained.
- Optional WorldGuard integration supported.
Note: If another plugin generates blood particles, disable its blood effects to prevent overlapping visuals.
🩸 PixelBlood — Bringing Combat to Life!
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:1oCiyYKI:BqcmswZc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1oCiyYKI:BqcmswZc"
}

