Links
Creators
Details
1.1.6-1.21.1
Compatibility
Changes
Blood Shambler
A new mini-boss that spawns during blood moons, one per player. It locks onto a single target and will not switch aggro. If needed, you can disable its spawning in the configuration file.
- Randomized stats on spawn (100–200 HP, 60–120 shield)
- Shield absorbs 80% of incoming damage; the remaining 20% goes to health
- Breaking the shield stuns it for 2 seconds and applies Weakness for 10 seconds. Shield fully regenerates after 1 minute
- Glows purple during blood moons with a boss bar showing shield/health status
- Teleports to its target when the distance is too far or when blocked by terrain it can't break through, with a short windup animation
- Emergency behavior at 30% HP: rallies nearby Blood Zombies to force-target the player, or begins Sanguine Drain — siphoning health from surrounding zombies to heal itself
- On death, converts a nearby zombie into a Blood Zombie as a final act
- Despawns when the blood moon ends
- The Shambler's destruction causes a small explosion, but any blocks destroyed will be restored after the blood moon ends (unless the player has placed new blocks there beforehand).
Scorching Eye
A new consumable item. Smelt a Blood Eye in a furnace (4 min cook time) to obtain it.
- Right-click to ignite all hostile mobs targeting you within a 10-block radius for 8 seconds. Consumed on use.
- With Apotheosis installed, the Scorching Eye can be socketed as a gem:
- Weapon: 30% chance to ignite targets on hit for 4 seconds. While they burn, all fire damage they take heals you (life steal).
- Armor: 30% chance to ignite your attacker on hit. Reflects 20% of incoming fire damage back to the source.
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:xacM17hx:yGzKep1L"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xacM17hx:yGzKep1L"
}

