1.7.3
Compatibility
Changes
🩸 Blood Horror Craft — 1.7.3 👁️ “The Jumpscare Update”
👁️ New Mobs 🦇 Vampire: A bloodthirsty night predator that stalks its prey as soon as darkness falls.
📱 Momo: A disturbing entity with a distorted face watching you from the shadows.
🤕 Scarred Man: A heavily scarred wanderer, aimless but deadly if he spots you.
💀 Hollow Husk: A hollow, corrupted shell driven by pure rage.
⚙️ New Mechanics & Effects Jumpscare Entities: Several mobs now feature terrifying jumpscares when getting too close to the player.
Static Screen Overlay: When facing major entities like Slender Man, your screen will be covered by intense TV static, blinding you completely during the panic!
Vanishing After the Scare: Jumpscare mobs now use an immediate Despawn/Discard mechanic right after terrifying you, making them vanish into thin air without dropping any accidental items or XP.
✨ Momo's Curse: A brand-new negative status effect linked to Momo's Mask ... handle with care.
⚔️ New Items, Weapons & Alchemy 🧪 Bleeding Potion Crafting: You can now brew a deadly Bleeding Potion using Pennywise's Fang as a core ingredient.
🧱 Bloody Brick: A heavy, blood-stained brick improvised for survival.
🦷 Pennywise's Fang: A sharp fang harvested from the clown, imbued with an evil aura and used for brewing.
🎭 Momo's Mask: Momo's unsettling face, to be handled with extreme caution.
⚙️ Fixes & Improvements AI Enhancements: Improved zone detection and tracking radiuses for several entities.
Audio Synchronization: Ambient and static sounds are now directly attached to the mobs to prevent endless sound loop bugs.
Balancing: Adjusted spawn rates across the world and fixed minor bugs.
🩸Blood Horror Craft Reborn 1.7.3 continues expanding the nightmare with dynamic jumpscares and brand-new stalkers. Stay alert... the darkness won't miss you. 👁️
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:3DpCCYth:Lip82nQT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3DpCCYth:Lip82nQT"
}

