CurseForge · Minecraft mod
Bloody Bits Fix
Fixes client crash (Ticking entity) in CravenCraft’s Bloody Bits v1.3.3 by safely handling CLIENT_SIDE_BLOOD_SPRAYS overflow and avoiding Map#get(0) NPE. Client-side only.
Quick answer
Which Bloody Bits Fix release should I use?
Bloody Bits Fix CravenCraft's Bloody Bits Fix targets 1.20.1 with Forge. The project page does not say whether this file belongs on the client, dedicated server, or both. No extra mods listed for this file.
Where it goes
Is Bloody Bits Fix required on the client, server, or both?
The project page does not say whether this file belongs on the client, dedicated server, or both.
The source does not explicitly classify this release as client-only or server-only.
What else does Bloody Bits Fix CravenCraft's Bloody Bits Fix need?
CravenCraft's Bloody Bits Fix. Change the file and its required mods may change too.
This file does not list any required mods. Do not add a library just because a different file uses it.
This file does not list any required or optional mods.
Before you install it
Add Bloody Bits Fix without breaking your instance.
Built for Bloody Bits Fix CravenCraft's Bloody Bits Fix. Pick another file and the loader, install side or required mods may change.
- 01
Stick to this file
Use CravenCraft's Bloody Bits Fix. It targets 1.20.1 with Forge; another release may have different loader, side or dependency requirements.
- 02
Bring the mods it needs
This file does not list any required mods. Do not add a library just because a different file uses it.
- 03
Put it on the correct side
The project page does not say whether this file belongs on the client, dedicated server, or both.
- 04
Pick the file you checked
Use the “Get this file” button beside CravenCraft's Bloody Bits Fix. It opens that exact file at the source.
About this project
What does Bloody Bits Fix add?
Bloody Bits Fix
A small compatibility patch for CravenCraft’s Bloody Bits v1.3.3 on Forge 1.20.1 that prevents client crashes (Ticking entity) caused by a NullPointerException in BloodSprayEntity#setClientBloodColor.
🩸 What Was Broken
When the internal CLIENT_SIDE_BLOOD_SPRAYS map overflowed, the original code called map.get(0) and attempted to access a null entry, leading to crashes during heavy blood-particle activity.
🧩 What This Fix Does
Rewrites the method via Mixin overwrite:
• Safely synchronizes state of respawned sprays (including life).
• When the limit (CommonConfig.maxSpatters()) is reached, removes the oldest entry instead of key 0.
• Calls discard() before removal.
• Fully eliminates all NullPointerException cases.
⚙️ Installation
1️⃣ Install Bloody Bits 1.3.3.
2️⃣ Drop bloodybitsfix-1.0.1.jar into your /mods/ folder.
✅ How to Verify
✔️ Spawn large hordes to generate blood sprays.
✔️ Confirm that no crash occurs.
✔️ The total number of splatters stabilizes around the configured maxSpatters limit.
🧠 Notes
• life duration behavior matches the original implementation.
• To further reduce visual load, lower maxSpatters in the Bloody Bits config.
🔗 Dependencies
Required: Bloody Bits (by CravenCraft)
💬 Community patch developed and tested by MsMurk — keeping Forge stable and bloody! 🩸
Project description from CurseForge.
Pick your setup
Bloody Bits Fix by Minecraft version and loader
Choose the version and loader you play, then open the matching release.
Check the dependencies, then try the file in a copied instance before changing a world you care about.
Recent files
Bloody Bits Fix versions and loaders
CravenCraft's Bloody Bits Fix
bloodybitsfix-1.0.1.jar
22 Oct 2025
Looking for an older file? The official CurseForge project page is in Resources.