Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated last month
All versions
1.2.5
Release
KubeJS TFC 1.2.5last year 1,012
Uploaded by
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Forge
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
- Fix faulty assumption that climate models will only be added to TFC-like worlds
- Slight rework to how custom climate models are created
- 'Advanced' climate model functionality has been mered into the regular custom model
- Along with this, there is now only a single
.registermethod in the event, the previous registration methods are now deprecated
- Along with this, there is now only a single
- TFC climate default accessors have been moved from the event to the model builder callback
- The wind vector callback now provides a
LevelandBlockPosinstead of aBlockContainerJS - Custom noises are now created differently:
- First,
.newNoiseis called with a callback where the noise can be modified, this returns an index - This index can be used in
.noiseto get the noise within calculation callbacks
- First,
- 'Advanced' climate model functionality has been mered into the regular custom model
- Spreading bush blocks are now tagged with
tfc:any_spreading_bushby default, fixing max height being ignored and cane blocks breaking - Add methods for setting the model and textures of bush blocks
- Cane block models are now named
<parent_id>_side_<lifecycle>_<stage>to match TFC's model naming scheme, previously they were named<parent_id>_cane_side_<lifecycle>_<stage> - Fix the use of
productItemwith a pre-existing item not working as it should - Add
/kubejs_tfc searchcommand, enabling pack makers to determine which data entries are applied to an item/block/fluid
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:IvDJQ46x"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mhtClB2S:IvDJQ46x"
}

