All versions
1.20.1-1.0.0
Release
TFC - Ars Flora Compat (Configurable Worldgen) 1.20.1-1.0.09 months ago 214
Compatibility
Minecraft: Java Edition
1.20.1–1.20.6
Platform
Forge
Supported environments
Client and server
Required content
Changes
Profile-based configuration per plant
- Individual TOML per profile under
config/tfc_ars_compat/.toml - Configurable:
biomes,rarity_chance,count_per_chunk,tries_per_patch,xz_spread - Profiles are generated automatically with default values on first launch
Slim JSON, values from runtime config
- Configurable patch feature (
config_random_patch) - Configurable placement modifiers (
config_count,config_rarity,config_biome_filter)
Server-friendly biome control
- Biome list per profile (IDs or tags such as
#minecraft:is_overworld,#tfc:…) - V****anilla/TFC soil compatibility
- Optional
minecraft:dirttag support (TFC grass and dirt variants) via datapack tag - Does not interfere with KubeJS setup (tags are additive;
replace=false)
✨ New Features
- Archwood groves now generate in TFC biomes (sparse by default).
- TFC fuel support for Archwood logs via
#forge:logs/archwood(optional-safe). Defaults: 700 °C, 1200 ticks per log.
✅ Fixes
- Sourceberries on hills: moved
heightmap+would_surviveto the inner bush placed feature so patches follow terrain naturally (no slicing).y_spreadeffectively locked to 0.
🔧 Improvements
- Kept the optional soil bridge (
data/minecraft/tags/blocks/dirt.json,replace:false) — only activates if your pack doesn’t provide one (e.g., via KubeJS). - Cleaned up data-driven setup and defaults for more consistent worldgen.
📎 Notes
- Takes effect in new chunks.
- No mobs included; recommend Spawn Balance Utility if you want Wilden spawns.
- Config path:
config/tfc_ars_compat-<profile>.toml(keys:biomes,rarity_chance,count_per_chunk,tries_per_patch,xz_spread).
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:3HtDNHqB:IGPUpCIM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3HtDNHqB:IGPUpCIM"
}



