Configuration - CravenCraft/BloodyBits GitHub Wiki
Config System
Bloody Bit's has a fairly in depth configuration system. It's broken up into two parts: The Common Config for changes related to the server and client, and the Client Config for changes just related to the client.
Common Config
This config mainly controls the amount of blood entities allowed at any given time, their despawn time, how close they have to be to any given player to trigger, and what entities do not bleed.
despawn_timeHow many ticks (20 ticks = 1 second) until a blood spatter/chunk will fully disappear. NOTE: spatters and chunks will slowly fade away or shrink based on this time. So, setting it as longer or shorter will increase or decrease this fade/shrink time respectively.bleed_when_damagedEntities will randomly bleedwhen their health drops below 50%. The lower their health drops below 50%, the more often they will bleed. The default is false.max_spattersHow many blood spatters can be in a given world at once. This is determined per world, NOT per player. So, having a relatively large number will make sense. The default is 2000.blood_spatter_volumeHow loud the blood spatters are when hitting a surface. The default is 0.75.blood_spray_distanceHow far blood will spray from an entity. Higher values means the blood sprays farther away. The default is 0.025.show_blood_chunksDetermines whether or not the mod should replace an entity's death poof particles with a spray of blood chunks. This could potentially be heavier on the server since it's introducing more entities. So, I left this as optional. This is on by default.solid_entitiesA list that determines what entities do not bleed. This generally includes entities likeskeletonsand thewither. Any modded entity can also be added to the list. Just make sure to include the mod prefix (e.x.,alexsmobs:bison).blacklist_entitiesSome mobs don't play nice with this mod, and may cause crashes. Players can define which mobs they want to blacklist that might be causing some issues by adding to the list. By default there is only one entity that is populated in the list since it is the only entity that I've found causes major issues with my mod: ["alexsmobs:cachalot_whale"].blacklist_damage_sourcesA list of damage sources that are blacklisted from producing blood sprays. A list of vanilla damage sources can be found here. The default list is ["onFire", "inFire", "starve", "drown", "hotFloor", "dragonBreath", "dryOut", "freeze", "lava"]
Client Config
This config controls whether or not mobs should show damage.
show_entity_damageDisabled by default. This setting doesn't do anything as of now. I'm in the process of completely remaking this feature, and it's slow going, but will potentially have some interesting effects in the future. Stay tuned! The rest of the client config all depends on the above config option, which as of now should be turned off to keep the mod stable. In the future entity damage will potentially be implemented, but as of now it does nothing.
Blood Colors
There is an additional folder that will be generated whenever the mod is first loaded in. That is the bloodybits_colors folder, and within that folder with be a JSON file titled entity_blood_colors.json. This JSON file will contain arrays that have hex color values for particular mobs. Any additional hex color with a list of mobs can be added to this file.
Example:
"#c832ff": [
"minecraft:enderman",
"minecraft:shulker",
"minecraft:ender_dragon",
"minecraft:endermite",
"minecraft:pillager"
]
"#c832ff"Represents the hex color value for the array. You can easily figure out what hex values are for what colors using any color picker online to generate a hex value (example)"minecraft:enderman"Is one of the items in the array. It represents the vanilla Minecraft Enderman, but you can add any modded entity to this list so long as you remember to include the mod's prefix (e.x.,"alexsmobs:tiger").