Tags
Creators
Details
All versions
26.1.2-1.1.18
Release
neovitae 26.1.2-1.1.1812 hours ago 11
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
1.1.18
New
- Added the Ritual of Sentient Penance. Stand on the master stone in your Sentient Armor and throw a downgrade catalyst onto it to take on that curse, freeing Upgrade Points to spend elsewhere. Downgrades could not actually be applied before; every catalyst shown in the book now works.
- Added two new downgrades: Poisoned Blood (periodic poison, from a Venomgland Sac) and Hollow Hunger (faster hunger drain, from a Hollow Gut).
- The book has a new Downgrades section covering every curse, its catalyst, and how to apply and remove them, plus new entries for the Sentient Penance ritual and the Skilled upgrade.
Changes
- The Ritual of Sentient Evolution now shows a message when your armor evolves, and tells you when it has reached its limit instead of doing nothing. The book now spells out the numbers: 100 points per evolution, up to 500.
- The Slow Heal downgrade is now named Diseased, matching its book entry.
Fixes
- Toggling the Lex Vitae's mode now shows the new mode on screen.
- The Lex Vitae's beam now mines with the selected 3x3 or 5x5 radius.
- The Lex Vitae's 3x3 and 5x5 mining now aligns to the face of the block you are targeting, not the direction your head is turned.
- An activated Lex Vitae now works as a weapon again: its attack damage and speed apply to your hits and show in the tooltip.
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:ZLufH8O5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rvaW4C93:ZLufH8O5"
}

