Tags
Creators
Details
1.1.0
Compatibility
Changes
Changelog
All notable changes to Revival Lives Shrine will be documented in this file.
[1.1.0] - 2026-03-03
✨ The Ritual Update
Revival Shrine Structure
-
Multi-block Requirement: The Shrine block no longer functions in isolation. It must now be placed atop a specific sacrificial altar to activate.
-
Altar Construction: Requires a 9-block base consisting of:
-
4× Obsidian (Corners)
-
4× Amethyst Blocks (Sides)
-
1× Crying Obsidian (Center - place the Shrine on top of this block)
-
Functional Validation: The Shrine now performs a real-time check for the underlying structure before allowing activation.
Visuals & Effects Overhaul
- Enhanced Ambient Effects: Upgraded the particle systems for a more "ethereal" feel. Added swirling Amethyst and Crying Obsidian-themed particles when the shrine is idle.
- Dynamic Activation: The 60-second countdown now features expanded visual feedback, including localized lighting effects and intensifying soundscapes as the timer approaches zero.
- Shrine Appearance: Refined the block model and texture for a more detailed, ancient aesthetic.
GUI & HUD Improvements
- Modernized HUD: The lives display has been polished with smoother animations and high-fidelity icons.
- Inventory Overlay: Re-designed the expanded status indicator (E key) with better padding, clearer typography, and a more intuitive layout.
- Sync Optimization: Improved the custom networking payload for even lower latency between server-side life changes and client-side HUD updates.
Technical & Compatibility
- Logic Refactoring: Updated the activation code to handle the new multi-block state checks efficiently.
- Compatibility: Fully verified for Minecraft 1.21.8 and Fabric Loader 0.16.x.
- License: Continued support under the MIT License.
Credits
- Created by The Void (itsvoid.com)
- Special thanks to Altocleffs and Nebulander
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:KTbuAF1s:MumR8Hb5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KTbuAF1s:MumR8Hb5"
}

