Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated 2 months ago
All versions
1.3.3
Release
KubeJS TFC 1.3.3last year 12.3K
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Forge
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
- The list ids command is now paginated
- Add several bindings for noises
- Add some additional helper functions for TFC's
Noise2DandNoise3Dclasses - Add noise inspection commands
- Fix
kubejs_tfc:wrappedchunk generators crashing when trying to find a spawn position - Describing a knapping type via command will now include the texture(s) used by the knapping screen
- Add support for Artisanal recipe types and ISMs
- Deprecate
#notAxisAligned()in ground cover builders as it created invalid block state files - Custom fallen leaves are now included in the
tfc:fallen_leavesblock and item tags by default, making them able to snow pile and turn into hummus by default - Custom (fallen) leaves can now be removed from automatic tinting by calling
#noDynamicTinting()on their builders - Tag ingredients printed via the describe command can now be clicked to use the
/forge tagscommand for that tag - Add TFC-specific recipe filters
- Add metal map in misc sub-binding
- Custom jar items now have the
tfc:jarstag by default - Add
#withoutCraftingRemainder()to the jar item builder - Properly implement input & output replacement for TFC recipe components & delegate recipe types
- Add
LayeredAreaconstructors to the misc sub-binding - Allow access to the chunk generator's
Settingsobject and creation ofRandomSources in the chunk data provider event - [Wiki] Commands now have their own page
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:XeAvj4GH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mhtClB2S:XeAvj4GH"
}

