Tags
Creators
Details
1.0.0
Compatibility
Changes
Changelog
All notable changes to Revival Lives Shrine will be documented in this file.
[1.0.0] - 2026-03-02
🎉 Initial Release
Core Features
- 10-life system per player with persistent server-side storage
- Spectator mode enforcement when all lives are lost
- Offline-mode (TLauncher) safe — tracks by UUID
Revival Shrine Block
- Custom craftable block (4 Diamonds + 4 Obsidian + 1 Eye of Ender)
- Activation requires rare items dropped nearby: 2× Nether Star, 4× Totem of Undying, 1× Beacon, 8× Diamond
- 60-second activation countdown with floating billboard timer above the block
- Color-coded countdown: green (30s+) → yellow (10–30s) → pulsing red (<10s)
- Auto-deactivation when timer expires
- Shrine self-destructs after reviving a player
Visual Effects
- Massive particle explosion on activation (Witch, End Rod, Dragon Breath)
- Continuous ambient particles while active (spiraling Witch, floating End Rod, Soul, Enchantment, Dragon Breath)
- Golden particle burst on revival
Lives HUD
- Always-on hearts display in top-right corner of the game HUD
- Expanded display when inventory is open (E key) with status indicator
- Color-coded: red (4+ lives), orange (1–3 lives), grey (0 lives)
- Real-time server-to-client sync via custom networking payload
Commands (all under /revivallivesshrine)
/revivallivesshrine lives— Check your remaining lives/revivallivesshrine revive <player>— Revive a fallen player (requires active shrine)/revivallivesshrine credits— View mod credits
Credits & Branding
- Created by The Void (itsvoid.com)
- Special thanks to Altocleffs and Nebulander
- Credit shown on first join (action bar)
- Clickable itsvoid.com link in
/revivallivesshrine credits
Configuration
config/revivallivesshrine.jsonwithdefaultLivesoption (default: 10)
Technical
- Minecraft 1.21.8 + Fabric Loader 0.16.x + Fabric API
- Java 21
- 1.21.8 APIs: ReadView/WriteView, PersistentStateType + Codec, FabricBlockEntityTypeBuilder
- MIT License
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:a6cEOHH8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KTbuAF1s:a6cEOHH8"
}

