Tags
Creators
Details
1.7.2
Compatibility
Required content
Changes
Added a Particle Effect for the Rite of Growth
Added the ability to put Malum Plants into Pots
Added Scarstone, Strangeroots and Strange Crystals
- These are rare new world generation features you can create by spreading blight
Added the missing Soulwoven Banner Pattern for the Wicked Spirit; Sword
Added new sounds for Brilliance and Natural Quartz Ore
Updated the charge-up particle effect for the Unwinding Chaos
Updated Blight Propagation particle effects
Updated the looks of various Blight Decals
Corrected some Codex entries
Corrected any use of the word "Aliment" in place of "Ailment"
Made the requirement for a blood sacrifice in the gease entry a bit more descriptive
Split the Totemic Runes entry across all the respective totem rite entries
Removed Runic and Cursed Sap Blocks
- These may return in the future, but at the moment I do not see a way to make them interesting
Fixed Spirit Infusion copying durability and attribute data from gear over to the result
- This is done through a blacklist tag for component types
Fixed a crash tied to the Sundering Anchor encountered when loading into a world with the thrown anchor loaded from memory
Fixed Arcanaphage Geas crashing when taking sourceless damage
Fixed Hereic Rune crashing when taking sourecless damage
Fixed detailed spirit descriptions still being wrong
Fixed certain totem effect particles appearing excessively
Fixed Create Recipe Compat Not Working
Fixed Raw Brilliance and Raw Soulstone becoming Raw Soulstone in Weeping Well Transmutation
Fixed the Malignant Stronghold Scarf remaining even when the associated entity is killed
Fixed the Geas Effect book page having misaligned text when using the easy reading book style
Fixed other stuff too
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:jgzwYsAN:jXmJQMxy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jgzwYsAN:jXmJQMxy"
}

