Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 3 years ago
Updated 2 months ago
All versions
2.4-b04a
Beta
Cold Sweat 2.4-b04alast year 16.9K
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
2.4-b04a
Fixes:
Technical Changes:
Fixes:
- Fixed gradually decreasing server performance due to registry leaks
- Fixed long freeze when exiting a world or server
- Fixed crash when loading TOML configs in some cases
- Fixed boolean block state values in JSON not being read properly
Technical Changes:
- (1.16) The file structure of JSON registries has changed to match that of other versions:
- Registries are now located in data/<yourmod>/cold_sweat/* (instead of data/cold_sweat/config/*)
- This means that JSON registries registered by other mods will have that mod's namespace in their IDs
- Datapacks still do not work. This is only for mod developers
- Block temperature JSON configs can now be added to "effect groups"
- Block temperatures in an effect group will count towards each other's max effect limits
- i.e. if redstone lamps and copper bulbs are part of the same group, redstone lamps will count towards the max number of copper bulbs and vice-versa
- Implemented via the "effect_group" field in block temperature JSON configs
- This field takes in a tag ID containing block temps (i.e. "yourpack:yourtag" [no #hashtag])
- Add your block temp tag to data/<yourpack>/tags/cold_sweat/block/block_temp/<yourtag>.json
- Include the IDs of the block temps in the tag (i.e. "yourpack:your_block_temp")
- registerByClassName() in TempModifierRegisterEvent now accepts constructor arguments as its last parameter (varargs)
- These arguments will be passed to the constructor of the modifier class upon creation
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| ColdSweat-2.4-b04a-sources.jar | Unknown | 1.44 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:374i8MZn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uXhSmPjd:374i8MZn"
}

