Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated 2 months ago
All versions
1.3.0
Release
KubeJS TFC 1.3.0last year 198
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Forge
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
- Add commands to print TFC's level settings and chunk data
- Add setting (default enabled) to deduplicate TFC datapack validation errors that are inserted into the KubeJS console
- Add chunk generator type
kubejs_tfc:wrappedwhich enables adding chunk data to levels without proper TFC-like level generators - New event for creating chunk data, depends on above chunk generator type
- De-hardcode dead crop model generation
- Add
tfc:torchblock builder type - Add
tfc:heatblock entity attachment type - Add
tfc:calendarblock entity attachment type - Deprecated:
#dripsintfc:thin_spikeblock type, same functionality handled by nullable parameter of#dripParticle#hasBubbles&#hasSteamintfc:springfluid type, same functionality handled by nullable parameter of#bubbleParticle&#steamParticle#allModelsin berry bushes, superseded by#models
- Remove deprecated methods in custom climate model event
- Remove old, non-functional chunk-data creation mechanism for custom climate models that was added in 1.2.6
- Add support for Kube's ingredient and result modifiers to TFC's advanced crafting recipes
- Fix drinkable description command printing the first effect in place of all-but-the-last effect
- Fix being unable to modify the cane block of spreading bushes
- Add the ability to properly modify the model generation of multi-model blocks (aqueducts, grass, gearboxes, etc.)
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:mhtClB2S:yKWHi4AC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mhtClB2S:yKWHi4AC"
}

