Tags
Creators
Details
4.6.0
Compatibility
Required content
Changes
Thermoo 4.6.0 for Minecraft 1.21.1: Polymer Integration
Thermoo can now once again work fully server side, but only if Polymer is installed. Some translations will be missing and custom command arguments will not autofill, but it will be compatible with vanilla clients or clients not using Thermoo. This only applies for dedicated servers, and not to LAN worlds in single player.
The release of this update should not be conflated to mean that I will be making a Polymer patch for Frostiful or Scorchful at this time, I mainly did this so that Thermoo can be used for custom datapacks on servers (which used to be a feature of Thermoo).
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:r7htDyPL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9TbXlAut:r7htDyPL"
}

