Tags
Creators
Details
All versions
1.4.1
Release
Create: Integrated Farming 1.4.1 for Create 1.21.1-6.0.102 months ago 2,920
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Create: Integrated Farming 1.4.1
Add
- Added a unified Roosting JEI category for Chicken Roosts and supported duck, goose, and turkey Roosts. Each entry shows optional item and fluid feeding, the natural production time, and outputs that can be identified from the active loot table.
- Added Roosting JEI entries for Vanilla Backport warm and cold chickens, Confluence ducks, Untitled Duck Mod ducks and geese, Environmental ducks, and Autumnity turkeys when those mods are installed.
- Roosting JEI information is supplied by the server and refreshes after joining or reloading data packs, so server-defined food data maps, food tags, and production loot tables are reflected without reconnecting.
Update
- Create Spout feeding now works with every supported occupied animal Roost, including duck, goose, and turkey variants, instead of only Chicken Roosts.
- The existing
create_integrated_farming:chicken_foodfluid data map remains the configuration point for Spout feeding. Existing data packs require no migration, and no separate JEI display format has been added. - Roosting JEI displays conditional or complex loot tables conservatively and does not invent uncertain outputs or probabilities.
- Updated the Roost Spout Ponder wording to refer to birds instead of only chickens.
Fix
- Spouts no longer begin feeding or consume fluid when a Roost is empty, on feeding cooldown, already has an output ready, or does not contain enough fluid for one configured feeding operation.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| create-integrated-farming-1.4.1-sources.jar | Unknown | 496.36 KiB |
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:9k1pAsfR:5plrrJxk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9k1pAsfR:5plrrJxk"
}

