Tags
Creators
Details
Licensed LGPL-3.0-only
Published 2 years ago
Updated 5 months ago
All versions
3.6.0
Release
thermoo-patches 3.6.02 years ago 1,063
Compatibility
Minecraft: Java Edition
1.21.1
Platforms
Fabric
Quilt
Supported environments
Client-side
Server-side
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Changes
Stellaris Patch and a Modular Rework
This release of Thermoo Patches includes a new patch for Stellaris and ships a large internal refactor that has split the mod into a multi-module project.
- Fixed Origins patch not applying Environmental Resistances and updated Origins temperature effects
- Added a new integration Patch for Stellaris.
- This patch is, as always, completely optional.
- The Stellaris patch makes each planet and celestial object have a temperature (and humidity) that roughly corresponds to its real life temperatures. All planets except for Venus have different temperatures for day and night.
- These temperatures are as follows:
- The Moon (Day): 400K, 0% humidity
- The Moon (Night): 140K, 0% humidity
- Mars (Day): 293K, 0.01% humidity
- Mars (Night): 210K, 100% humidity
- Mars (Day, Ice Spikes): 210K, 50% humidity
- Mars (Night, Ice Spikes): 120K, 100% humidity
- Venus (Day & Night): 737K, 0.01% humidity
- Mercury (Day): 700K
- Mercury (Night): 140K
- The mod has also undergone a major refactor that has split each patch into its own "sub mod" of the larger Thermoo Patches. I have tested this change as thoroughly as I can, but if there is something wrong do not hesitate to report it at https://github.com/TheDeathlyCow/thermoo-patches/issues
- As part of this change, the Armor Points++ and Immersive Weathering patches have been disabled, though not removed. I will update and re-enable these patches if and when those mods update.
- Because the Armor Points++ and Immersive Weathering patches have been disabled, Thermoo Patches is no longer incompatible with those mods, yay!
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Unavailable version
Any compatible version
Any compatible version
Any compatible version
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:TYRF9nUy:lGQsazkZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:TYRF9nUy:lGQsazkZ"
}

