Tags
Creators
Details
Licensed MIT
Created 4 years ago
All versions
1.20.1-1.2.3
Release
Farmer's Delight 1.2.3 - 1.20.13 years ago 281K
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
Additions
- Added certain blocks to the
create:brittletag, to prevent them from being deleted randomly when disassembling contraptions; - New tags:
farmersdelight:flat_on_cutting_board: Items which will always render flat and 2D when placed on a Cutting Board, to fix certain render cases.- Includes Trident and Spyglass by default, due to unique render cases;
- Optionally includes items from a few mods, such as Autumnity's Turkey and Supplementaries' Quiver;
Updates
- Updated method of modifying stack sizes for BowlFoodItems:
- Changes are now done on game start, rather than calculated during
maxStackSize()calls; - The
overrideAllSoupItemsconfig option has been removed, due to performance and usability concerns;
- Changes are now done on game start, rather than calculated during
- Cooking recipes will now drop sensible remainders for vanilla items which don't have them configured;
- (1.20) Updated Basket textures to match the new Bamboo design and palette;
Fixes
- Fix potential performance issues involving the stack size override for BowlFoodItems (see above);
- (1.18.2) Rollback and replacement to previous fix for Cutting Board's rendering issues with perspective items:
- The previous fix fails (and may crash) with some resource packs on 1.18.2, due to differences in how the method operates. On 1.19+, the fix works as intended;
- Instead of applying perspectives to determine 3D items, the
flat_on_cutting_boardtag will be used instead. Wrongly-angled items should be added to this tag;
Translations
- Updated:
- ko_KR (thanks, Yusi0!);
- pl_PL (thanks, jogurciQ!);
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:R2OftAxM:k7RoRFPF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:R2OftAxM:k7RoRFPF"
}

