Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated last month
All versions
1.3.2
Release
KubeJS TFC 1.3.2last year 2,286
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Forge
NeoForge
Supported environments
Client and server
Required content
Changes
- Add
#hasPostProcessand#emissiveRenderingmethods to extended properties - Add fissure, forest, forest entry, overlay tree, random tree, stacked tree, and krummholz worldgen builders
- Add direct wrapper for TFC's
ItemStackProvider - Fix double crops not having yield multipliers in their loot tables
- Add convenience method for setting the dead model of torches
- Add TFC sapling & leaf block builders
- Rename several methods in crop block builders to prevent Rhino throwing a fit when used
#productItem(ResourceLocation)->#existingProductItem(ResourceLocation)#model(number,Consumer)->#setModel(number,Consumer)#model(Consumer)->#setModel(Consumer)#texture(number,String)->#textureAt(number,String)#texture(number,String,String)->#textureAt(number,String,String)
- Allow
RecipeJS#getOriginalRecipeIngredients()to work with TFC recipe types - Add ability to change custom crop growth and expiry rates
- Add
alwaysandnevershortcuts for extended property settings that takeStatePredicates - Add tree solver command for modpack makers to easily make tree structures with proper states
- Add event for registering ISM -> json converters. All TFC, Firmalife, and TFCCC ISM types should be handled by default
- Add the ability to retrieve
NormalNoises during the chunk data provider creation event - Adds sealable inventory attachment which applies a food trait to items within it
- "Fix" proto chunks with no
ChunkDatacausing issues when promoted to level chunks with custom chunk data providers - Add custom surface rule source that uses the
RockSettingsat a given position - Fix custom spreading and double crops not respecting custom textures set in scripts
- This involved some reworks for all crop resource gens, the only noticeable effect should all stages looking for the same texture instead of unique ones, by default
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:bHmFGg9y"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mhtClB2S:bHmFGg9y"
}



