1.0.0
Compatibility
Required content
Changes
📜Origins: Wither Unleashed 1.0.0 - Changelog
The pack significantly enhanced the Wither's arsenal with new abilities to elevate the challenge and engagement of the battle. The key modifications and introductions are outlined below in technical terms for clarity:
Cataclysmic Demise
- Functionality: On death, the Wither now triggers a substantial explosion.
- Implementation:
- Action:
origins:action_on_death - Parameters: Explosion of power level 2, destruction type set to "break", without self-damage or fire.
- Action:
Heart of the Nether
- Functionality: The Wither's max health is boosted to a remarkable total of 600 hearts.
- Implementation:
- Attribute Modification: Increase of 300 to max health.
- Modifier Details: Applied as an addition operation on
minecraft:generic.max_health.
Nether Blitz
- Functionality: Periodically, the Wither executes a high-speed dash that generates a shockwave, inflicting Wither effect, blindness, and slowness.
- Implementation:
- Interval: Every 600 ticks.
- Composite Actions: Combination of velocity addition, sound effects, particle effects, and an area effect that applies multiple impacts.
Skeleton Summoning
- Functionality: When health drops below 500, the Wither summons Wither Skeletons, each carrying a stone sword and belonging to a predefined team.
- Implementation:
- Condition: Health ≤ 500.
- Actions: Sequential entity spawning with integrated delay and special effects, reinforcing thematic consistency with soul fire flame particles and characteristic sounds.
Nether Blast
- Functionality: Wither Skulls fired by the Wither now deliver 25% more knockback.
- Implementation:
- Attribute Modification: Knockback attribute of the skulls enhanced by multiplying the total by 1.25.
- Effect Details: Specifically modifies
minecraft:generic.attack_knockback.
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:rc3CpkT4:RUbRI3w4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rc3CpkT4:RUbRI3w4"
}

