Tags
Creators
Details
Licensed LGPL-3.0-only
Published 3 years ago
Updated 2 days ago
All versions
4.3
Release
Thermoo 4.32 years ago 52.3K
Compatibility
Minecraft: Java Edition
1.21.1
Platforms
Fabric
Quilt
Supported environments
Server-side
Client and server
Required content
Any compatible version
Any compatible version
Changes
- Added
getmethods to theTemperatureAwareclass that allow the interface to be obtained fromLivingEntityandEntity. Primarily intended for cases where interface injection may not work well. - Added translated for the consumable tags
- Replaced the attribute base value method of the environment controller with dedicated events. The old controller method has been deprecated. See PR #43
- Entity tags and lists are now allowed in the temperature effect
entity_typefield as a#prefixed tag ID or list of direct entity type IDs. See PR #42 - Fixed the
remove()temperature effect method not being called/tracked properly per entity. In particular, this fixes an issue where attribute modifier temperature effects would behave weirdly - The constructor for the
ConfiguredTemperatureEffecthas been marked as internal. The previous constructor has been kept to avoid a breaking change, but it has now also been marked as internal. - Deprecated
ConfiguredTemperatureEffect#applyIfPossible()(replaced with anapply()method that returns success instead). - Deprecated
ConfiguredTemperatureEffect#entityType()- use the newentityTypes()method (plural) - Deprecated
TemperatureEffects#getEffectsForEntity- this method should not have been part of the API and will be removed - Added
TemperatureEffects#getEffectthat allows for looking up a configured temperature effect by ID - The "resource conditions were not met" log has been moved to debug, which should reduce log spam caused by Thermoo
Supplementary resources
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:9TbXlAut:o40BDiH8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9TbXlAut:o40BDiH8"
}

