Tags
Creators
Details
1.21.1-1.1.0
Compatibility
Required content
Changes
1.1.0
Additions
- A Spiritus Gem placed in the Hellfire Forge now steadily draws Spiritus from the surrounding Aura, keeping it topped up so the Forge can craft on its own. Feed the local Aura and it runs unattended.
- While you are carrying a Spiritus Gem, walking over loose Spiritus you have no room to store now discards it instead of piling up in your inventory. Without a gem, the Spiritus is collected as an item as before.
- Neo Vitae is now available in Brazilian Portuguese.
Fixes
- Ancient Debris fragments and gravel now follow the same naming pattern as every other ore's fragments and gravel, so item filters and automation that sort by name treat them consistently.
- Decorating an Ara Vitae with torches, soul torches, or Blood Lamp lights around its pillars no longer causes the altar to lose a tier. Those optional pillar spots now accept decorative light sources.
- The Master Routing Node's energy rate field now shows your configured FE/t when you reopen the menu, instead of resetting to 500.
- The upgrade slot tooltips in the Master Routing Node no longer overlap into unreadable text when an upgrade is installed in the slot.
- Holding an anointed explosive charge while breaking blocks no longer drains its anointment.
- The Harvest ritual now gathers tall bamboo into its output instead of dropping most of it on the ground.
- Spiritus Crystals no longer spam the log with harmless warnings while resources load.
- Neo Vitae's station recipes (arrays, alchemy table, flasks, and living armor downgrades) are now marked special for better vanilla recipe book compat.
Note
This release is minimally breaking. Existing worlds are safe: the Ancient Debris items you already have keep working and look the same. Modpack makers who want the tidier internal names can delete the Neo Vitae materials config so it regenerates with the updated values.
Optional dependencies
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:rvaW4C93:PWVEq528"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rvaW4C93:PWVEq528"
}

