Tags
Creators
Details
1.0.0
Compatibility
Required content
Changes
Recipe Book Ferret
Features
This simple quality-of-life mod makes recipe books from crafting tables and player inventory consider and use contents of nearby chests when determining which recipes can be crafted.
There is no in-game UI. It all happens automatically.
If a recipe is deemed craftable based on the player inventory + container contents, when the player clicks on the recipe book entry's icon, ingredients will be pulled from containers if necessary to fill the crafting grid.
If the player closes the crafting screen while container-sourced ingredients are still inside the crafting grid, those items are returned to their original container.
Currently Covers:
- Regular chests (including copper chests)
- Shulker Boxes
- Ender Chests (optional, off by default)
- Chests inside Boats or Minecarts
- Chests attached to saddled Mules
- Bundles inside the player inventory
- ..theoretically any in-world entities implementing
Container.
ModMenu Options:
- container search area size: default search area is a 21x21x21 (radius=10) block space centered on the player (not the crafting table). This can be expanded up to 53x53x53, or reduced to 3x3x1.
- toggle EnderChest inclusion in container search. Defaults to off.
Compatibility & Limitations:
- Currently only supports single player worlds. Multiplayer/Server support has not been implemented or tested yet.
- Not tested with alternate crafting table-like items from other mods (example: Conquest Reforged's Sawhorse)
- Vanilla MC Furnace recipe books are able to see the contents of nearby containers (and will show matching recipes as craftable), but items will not be pulled into the furnace crafting grid when you click on the recipe icon.
- Chest, Ender Chests, and Shulker Boxes must be placed as blocks in the game world in order to be considered.
Built for:
- Minecraft 1.21.11
- Fabric Loader 0.18.4
- Fabric API 0.141.2+1.21.11
Other Mod Requirements:
- YACL 3.8.2+
- ModMenu 17.0.0-beta.2+
License
CC0
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:R9R13OCU:RO5lQTMW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:R9R13OCU:RO5lQTMW"
}

