1.2.0
Compatibility
Changes
New Content
New Mechanic: Mounted Bloodsucking Attack
The Bloodsucking effect has been completely reworked. It is no longer a simple "heal on hit" effect!
New mechanics:
When attacking, if the attacker has the Bloodsucking effect, they will mount the target and gain health regeneration.
The original passive ability remains: gaining experience still converts into health recovery (experience-to-life conversion).
New Status Effect: Corruption
How to obtain: Applied via the Corruption enchantment.
Effect:
Each time the player attempts to heal, there is a chance to trigger backlash.
When triggered: healing is cancelled, and the player takes damage equal to half the healing amount.
High-level Corruption will completely block traditional healing methods.
New Item: Rage Core
How to obtain: Crafting.
Effect: Consuming it applies the Rage effect for 3 minutes.
Rage effect:
Health ≤ 50%: Grants Strength II
Health ≤ 20%: Grants Strength III
The lower your health, the higher your attack power!
Mechanic Adjustments & Optimizations
Bloodsucking · Experience-to-Life Conversion
Healing formula optimized: duration = experience / 10 ticks, max 100 ticks per single trigger.
Negative experience (e.g., from enchanting) no longer triggers healing.
Mounted Bloodsucking (1.2.0 Core Update)
The entire Bloodsucking mechanic has been redesigned, evolving from "numeric healing" to "interactive healing".
Attacker mounts target -> continuous health drain and recovery -> burst damage upon dismount.
Supports tiered scaling (low levels = burst damage, high levels = sustained DOT).
Health Pact Display Optimization
Migrated from "action bar messages" to a screen overlay (HUD).
More stable, no longer conflicts with other action bar information.
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:TN9SrguL:n8nFQ1I4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:TN9SrguL:n8nFQ1I4"
}

