Tags
Creators
Details
4.7.0
Compatibility
Required content
Changes
Migration to Mojang Mappings
This is a backport of Thermoo 8.1.0 for Minecraft 1.21.10
Based Mojang's move towards removing obfuscation, and anticipating Fabric's move to MojMap, I have remapped Thermoo to MojMap. This was a big change code-side for Thermoo but, thanks to intermediary, this should not constitute any breaking changes to the public API. However, I may have messed something up, so this version will initially be released as a beta.
While no breaking changes are planned to be made at this time, a few fields and methods have been renamed to better conform to Official Mappings standards. These are as follows:
EnvironmentProvider.ENTRY_CODEC->EnvironmentProvider.HOLDER_CODECLightThresholdLightProvider#lightType->LightThresholdLightProvider#lightLayerAttributeModifierTemperatureEffect$Config#id->AttributeModifierTemperatureEffect$Config#locationScalingAttributeModifierTemperatureEffect$Config#id->ScalingAttributeModifierTemperatureEffect$Config#locationEnvironmentTickContext#world->EnvironmentTickContext#levelTemperatureEffects.STATUS_EFFECT->TemperatureEffects.MOB_EFFECT
The resource location of the temperature effect type thermoo:status_effect was changed to thermoo:mob_effect, however an alias has been added to allow existing datapacks to continue to work.
All old fields and methods have been deprecated and just redirect to the new ones, so there are no breaking changes.
When Minecraft fully moves over to using the unobfuscated jar (the update after Mounts of Mayhem), the old fields will be removed and other names, particularly class names, that could not be easily changed without breaking the public API will also be changed.
Optional dependencies
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:DCbTCdgs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9TbXlAut:DCbTCdgs"
}

