Tags
Creators
Details
Licensed MIT
Published 4 months ago
Updated 3 months ago
All versions
1.21-1.5.1
Release
Yet Another Thirst 1.21-1.5.13 months ago 74
Compatibility
Minecraft: Java Edition
1.21β1.21.1
Platform
Fabric
Supported environments
Client and server
Changes
Added
- EnvironmentZ Compatibility: Dynamic integration with EnvironmentZ for temperature-based dehydration modifiers and HUD integration:
- Dehydration rate modifiers based on player body temperature (
playerTemperature) with configurable temperature tiers (environmentzTemperatureTiers). - Configuration option
environmentzReplacesEnvironmentModifiersallowing EnvironmentZ body temperature to override standard environmental dehydration factors (biomes, altitude, heat sources). - Customizable temperature text overlay rendered next to the thirst bar and aligned with EnvironmentZ's thermometer HUD icon, with options for display type (
PLAYERbody temperature orTHERMOMETERambient temperature), temperature unit (e.g.Β°C), position offsets, and text color (environmentzShowTemperatureText,environmentzTemperatureTextType,environmentzTemperatureTextUnit,environmentzTemperatureTextXOffset,environmentzTemperatureTextYOffset,environmentzTemperatureTextColor). - Expanded
/thirst querycommand output to display EnvironmentZ body temperature, thermometer reading, and active dehydration modifier.
- Dehydration rate modifiers based on player body temperature (
Fixed
- Damage Type Knockback: Added custom damage type tag
minecraft:tags/damage_type/no_knockback.jsonto prevent unwanted knockback when taking dehydration damage. - Config Auto-Healing (Fabric): Added
addMissingKeysutility for Fabric JSON configurations to automatically inject newly introduced config options into existing user config files without overwriting saved settings.
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:HOl2fYpO:txnSJ7pl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HOl2fYpO:txnSJ7pl"
}

