Links
Tags
Creators
Details
Licensed CC-BY-NC-ND-4.0
Published 4 days ago
Updated 17 hours ago
All versions
1.2.0
Release
Tithe 1.2.02 weeks ago 8
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client and server
Required content
Changes
Breaking: /tithe admin history has been removed. Use /tithe admin set revivals <player> <n>, which takes a target instead of acting on whoever ran it.
Fixed
- Primal Embers were credited to the wrong objective. Embers now only pay off the objective naming the creature they came from, instead of the first outstanding mob objective swallowing everything in your pack.
- Players revived while offline were not moved to the altar when they logged back in.
- Reviving a player who was still on the death screen ran the ritual twice, once at nobody and once for real.
Added
- The return is now a ceremony. The revived player is pulled to the altar as a spectator when it begins, held there while the column builds, and handed back to survival on the Totem burst.
- Reviving a player who is offline sends a rising soul helix into the sky at the altar. Their own ceremony runs at that altar when they next log in.
- Operator commands:
/tithe admin stats,deaths,set,revive,rerollandreset confirm. Player arguments accept offline profiles, since anyone waiting is likely to be logged out. - The ledger now counts deaths as well as revivals. A death that is never paid off raises neither the toll nor anyone's weight, so nothing recorded it before.
Notes
- Reviving someone who is sitting on the death screen waits for them to press the screen's own button before the ritual starts.
rerollkeeps the existing quest's identity, so a dropped journal and any embers already earned stay valid.
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:V65X6rO8:hVfr8mKo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:V65X6rO8:hVfr8mKo"
}



