Tags
Creators
Details
All versions
3.0.4
Release
Bountiful Fares 3.0.47 months ago 8,331
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Bountiful Fares Version 3.0.4
Changes
- Items that fill Fermentation Vessels with water are now determined by tags
- NOTE: While items from other mods can now be added to this tag, they won't drop remainder items if they wouldn't in crafting!
- Flour particles now use a new rendering method, making it far harder to see inside of them
- Changed how Jack o'Straws are registered in code - because of this, automatic integration with dye mods should be much easier now
Fixes
- Fixed Walnut Leaves not being flammable
- Updated the particle renderer for flour to fix some rendering issues
Compatibility
- Added integration with Delicate Dyes
- Added assets for Shulker Tiffins & Jack o'Straws
- Added integration with Every Compat (Wood Good)
- Other integrated mods' wood types will have trellis and pickets variants
- Other mods' wood blocks will have hoary and walnut variants
- Changed the way fermentation recipes are displayed with EMI
- Now instead of the old GUI-like display, the recipes are displayed as "vessel + input -> output" similar to the world interaction recipes in EMI
- Added support for tiffin coloring recipes in EMI
- Teas in cauldrons no longer return Glass Bottles instead of Cups when Amendments is installed
- Fixed a tag issue in the recipe for Fish Stew when cooking in a Farmer's Delight cooking pot
New Features
- Added configuration values for generation features
- The generation of all trees, wild crops, and Grassy Dirt patches can all be toggled
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:YgrSDjlb:Az3qVNru"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YgrSDjlb:Az3qVNru"
}

