Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 3 years ago
Updated last week
All versions
2.4.4
Release
Cold Sweat 2.4.4last week 8,588
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
2.4.4
Fixes:
- Updated for Minecraft 26.2 (ALPHA!)
- Revamped how water temperature mechanics work:
- Each biome now has an explicit "freezing point" temperature at which water freezes into ice
- This temperature is typically higher for colder biomes, and lower for warmer biomes
- This can be defined in TOML, JSON, and KubeJS configs
- This is to help reduce cases of water freezing and melting when it shouldn't
- Water temperature now represents an absolute value, rather than an offset to the biome's temperature
- For example, a biome can have a temperature of 80 degrees, and a water temperature of 60 degrees
- Water is now the same temperature regardless of time of day (since it's no longer linked to biome temperature)
- Existing configs that define water temperature as an offset will be automatically converted to the new system
- Each biome now has an explicit "freezing point" temperature at which water freezes into ice
- The icebox will now always produce mist particles like it did in older versions, not just when powered or when cooling waterskins
- Cold Sweat's JEI recipes will now combine recipes for items that belong to the same tag
Fixes:
- Fixed entity configs taking up more memory than they should (thanks to RinkyDinkyNooble on GitHub)
- Fixed the soulspring lamp not being held correctly while eating or using two-handed items (bow, crossbow, etc.)
- Fixed boiler, icebox, hearth, and sewing JEI recipes not being discoverable by clicking the block in JEI
- Fixed mods crashing if they rely on Cold Sweat's pre-2.4.3 block temperature system
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| ColdSweat-2.4.4-sources.jar | Sources jar | 1.61 MiB |
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:uXhSmPjd:UGoodVYD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uXhSmPjd:UGoodVYD"
}

