Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated last month
All versions
2.1.0
Release
KubeJS TFC 2.1.0last month 697
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
- Add support for FirmaLife recipes
- Add events for creating FirmaLife and Beneath data types
- FirmaLife and ArborFirmaCraft recipes types and Beneath and FirmaLife data types can now be used in the data type commands (
/kubejs_tfc <search|describe|list_ids>) - Internal validation for
DataManager/DataTypesynchronicity is now opt-in- Use
systemProperty('kubejs_tfc/assert_all_data_managers_have_data_types', 'true')in your run configs if you wish to enable this in dev environments
- Use
- Update to TFC 4.2.8, which is now the minimum version
- The nutrient amount in
FoodDatas are now specified by specifying each nutrient name instead of anutrient: number[5] #deposit,#support,#itemDamageResistance, and#entityDamageResistancein theTFCEvents.dataevent now have 1(+1) params to match the majority of the other methods in the event- Also like the majority of the other events, the first param is a map of parameters to values and the second parameter is an optional id
- The old forms of the methods still exist but will log a warning and will be removed in a future version
- As always, see the docs for the new form of the methods
- The models used for
#groundcoverModelShapein the groundcover block builder have been tweaked to respond semi-automatically to TFC makes to its own groundcover models- The driftwood and stick shapes have been split into several different models
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:rsBv9bL5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mhtClB2S:rsBv9bL5"
}

