0.3.0-rc2
Compatibility
Changes
Effect Adjustments
All negative effects of "Absolute Failure" Enchantments are uniformly changed to the potion effect format for display, allowing players to intuitively check the specific effects currently in effect.
Absolute Failure: Hunger
Adjusted to "immediately empties the player's hunger bar, and the player cannot restore hunger or saturation for the duration of the effect."
Absolute Failure: Freeze
Adjusted to "the entity takes continuous freezing damage for the duration of the effect."
⚠️ Note: After the effect ends, due to in-game mechanics, the entity requires additional time to recover from the frozen state. Therefore, the actual freezing duration will be slightly longer than the duration of the Absolute Failure: Freeze effect.
Absolute Failure: Burning
- The burning state applied during the effect duration: even if extinguished with water, the entity will re-ignite immediately after leaving the water source;
- If triggered simultaneously with "Absolute Failure: Freeze," the entity cannot catch fire due to the frozen state, but will still take a certain amount of burning damage.
Absolute Failure: Suffocation
Adjusted to "immediately empties the player's oxygen bar, and the player cannot restore oxygen for the duration of the effect."
Bug Fixes
Fixed the abnormal interaction distance issue for "Absolute Failure: Block Proximity" and "Absolute Failure: Entity Proximity".
Original Issue: After an entity triggers the above effects, dies, and respawns, the block interaction distance and entity interaction distance cannot be restored. Neither "death and re-entry" nor "quitting and re-launching the game" could resolve this problem.
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:XrXU132T:ru1CabLL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XrXU132T:ru1CabLL"
}

