Tags
Creators
Details
All versions
3.0.5
Release
Bountiful Fares 3.0.57 months ago 7,708
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.5
- This mod now requires NexusLib version 1.1.4.
Changes
- Spongekins can now be sheared by a Dispenser with Shears inside
- Shearing Spongekins now emits the "shear" game event
- Fermentation Vessels won't spawn fermentation particles that would have been inside themselves, thus reducing particle count
- Fermentation recipes now support item tags as the ingredient
Integration
- EveryCompat's added trellises/pickets now copy block properties of Bountiful Fares's ones
- As a result, added trellises now have proper occlusion, and grow crops on themselves properly
- Fixed loading the mod with Farmer's Delight spamming the logs with recipe errors on loading a world
- Fixed disabling the EveryCompat creative tab crashing the game when Bountiful Fares is installed
- Added recipe compat with Wilder Wild for Coconuts and Split Coconuts
- Fermenting recipes using ingredients of Oranges, Lemons, Plums, and Coconut halves now use common tags for the ingredients, meaning mods like Nature's Spirit, Atmospheric, or Environmental's versions of these items can be used
Fixes
- Infused Candles (+ Coconut Candles) can now properly be lit with Flint & Steel from Dispensers
- Particles when shearing Spongekins now syncs between clients
- Bountiful Fares' icon now shows up properly in mod viewers
- Added note block instruments to Neoforge version (previously fabric only)
- Tea Cups now properly display 5 minutes of Ebullience instead of 3
- Hoary & Walnut Signs (& Hanging Signs) placed on a wall no longer drop Oak variants
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:ldSCDIGz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YgrSDjlb:ldSCDIGz"
}

