All versions
1.21.1-1.0.27
Release
neovitae 1.21.1-1.0.272 days ago 202
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
1.0.27
Additions
- The Syringe Throwing Dagger now draws blood from creatures it kills, dropping Tabula Ampoules; tougher creatures yield more.
Changes
- The great art overhaul is here! Over 170 items across Neo Vitae have been redrawn from scratch with fresh, hand-crafted pixel art: reagents, tools, sigils, flasks, ritual gear, and everything in between. Anointments now each carry their own distinct icon as well. It's the biggest visual update in the mod's history, and it gives the entire collection a cohesive, hand-made feel.
Fixes
- The Spiritus Aura Gauge now keeps its readout on screen while worn in a Charm or Sentient Armour socket, rather than only when carried in your inventory.
- The Scriptura Vitae now explains how Spiritus Gems are actually charged: saturate a chunk with the Aspect you want, then place the gem in a Vas Maleficum and give it a redstone signal. It also warns that any Raw Spiritus lingering in the chunk will claim an empty gem before any other Aspect gets a look in.
- The Aspects of Spiritus entry no longer shows a picture of a ritual that has nothing to do with splitting crystals.
- The Lex Vitae now breaks cobwebs quickly, the way a sword or paxel does.
- Fixed the Scriptura Vitae showing an error notice on its recipe pages (such as the Tabula Vitae entries) after the book reloaded, instead of displaying them normally.
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
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:CCi4nM5F"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rvaW4C93:CCi4nM5F"
}

