Tags
Creators
Details
4.2.0-1.21.1
Compatibility
Required content
Changes
🐔 Roost Ultimate – Patch Notes
✨ Added
- Added custom Chicken Pipes for testing purposes.
- Added Name Field and Auto Output to:
- Breeder
- Soul Extractor
- Trainer
- Roost
- Added Output Level Control to the Trainer.
- Added Breeder and Soul Extractor to the Collector Whitelist.
- Added Breeder and Trainer to the Feeder Whitelist.
- Added Recipe Information for Breeding and Roost Output directly to the chicken descriptions.
- Added improved CC:Tweaked support for all blocks.
- Usage examples can be found on the wiki:
https://tarantel.gitbook.io/roost-ultimate/1.21.1/cc-tweaked-api
- Usage examples can be found on the wiki:
🔴 Redstone Control Changes
- Redstone signals now enable/disable Auto Output.
- If Auto Output is enabled via GUI, the redstone signal will be ignored.
🔧 Data & Config Changes
-
Moved
chicken_config_v*.jsonfrom:config/roostultimate/toinstallfolder/crlib/ -
Reworked the entire content handling system:
-
Every new entry in
chicken_config_v*.json(insidecrlib/) now automatically generates:- A new item model in
crlib/resources/assets/chicken_roost/models/item/ - A new
en_us.langentry in
crlib/resources/assets/chicken_roost/lang/ - Item tag entries:
c:roost/tieredc:roost/tier1toc:roost/tier9(based on chicken tier)
- A new item model in
-
It is now possible to reuse recipes already defined in
chicken_config_v*.json.
An example JSON can be found inside the mod JAR.
📦 Library Changes
- Split the Fluid Egg logic and several side features into a new library mod: CRLib.
- CRLib is now required to run Roost Ultimate.
- The new Mod + LibMod data handling makes adding new chickens much easier:
- Add a new config entry and the mod automatically creates:
- Item model
- Language entry
- Item tags
- For textures, you can reuse existing ones or provide your own.
🐞 Fixed
- Fixed button flickering in the Feeder and Collector screens.
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:YzR4F72D:IZNgnUi2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YzR4F72D:IZNgnUi2"
}

