Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 3 years ago
Updated 2 months ago
All versions
2.3.12
Release
Cold Sweat 2.3.12last year 4,496
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
2.3.12
Fixes:
Technical Changes:
Fixes:
- (1.21) Fixed crash loading KubeJS integration when Architectury is not installed
- (1.21) Fixed crash when initializing the creative menu in some cases
- Fixed removing insulation in the sewing table duplicating the insulation item
- Fixed crash when the player is wet on a dedicated server
- Fixed NBT arguments in JSON not parsing correctly in some cases, especially with nested compound tags
- Fixed TOML block temp configs being invalid if any string arguments contain only whitespace (" ")
- Fixed the "range" field in entity temperature JSON configs taking its value from the "temperature" field
- Fixed overlapping thermal sources still conflicting in some cases
- Fixed KubeJS registry events firing twice
Technical Changes:
- Added a "temperature" field to entity requirement JSON:
- Allows for checking the temperature of the target entity
- Represented as a map of string keys and double or double-range values
- i.e. {"body": 50.0} or {"world": {"min": 1.0, "max": 2.5}}
- The "cs:contains" NBT operator has been split into "cs:contains_all" and "cs:contains_any"
- "cs:contains_all" checks if the NBT list contains all of the specified keys
- "cs:contains_any" checks if the NBT list contains any one of the specified keys
- Added CreateRegistriesEvent.Pre
- Fires directly after registries are compiled, and before removals are handled
- Subscribing to the base event is not recommended, as it will cause the subscriber to fire twice
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| ColdSweat-2.3.12-sources.jar | Unknown | 1.33 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:tjUSvl0l"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uXhSmPjd:tjUSvl0l"
}

