Tags
Creators
Details
Licensed CC-BY-NC-SA-4.0
Published last year
Updated 4 months ago
All versions
1.0.1
Release
1.0.1 Hotfixlast year 192
Compatibility
Minecraft: Java Edition
1.21.7–1.21.8
Platform
Data Pack
Changes
#1.0.1 - Hotfix
This quick update fixes a few errors found in the 1.0.0 version. It's highly recommended you use this version instead of 1.0.0!
Big Structural Changes
- The data pack and resource pack have been merged into one file, that can be used as both
- Added a settings menu, available through commands. Current settings allow you to disable the welcome message, custom trades, random Villager names, and the updated fishing and Sniffer loot tables
- Updated the "welcome message" shown to new players. It's now better designed, includes links to the download and license, and notifies you if you don't have the resource pack enabled.
- Removed the "Vanillabean Info" menu (its purpose is better served by the welcome message)
- All custom recipes get unlocked when a specific item from them is obtained (like how default Minecraft recipes are). The exception here is the Pitcher Slab's recipe. It will be obtained in a different way soon
Loot Updates
- Apple Pies can now be found in Plains Village Chests
- Sweet Berry Cookies can now be found in Taiga Village Chests
- Spawner Fragments and Slimeballs can now be found in Monster Room Chests
- Chorus Carrots can now be found in End City Chests
- Slime Helmets can now be found in specific Trial Chambers Barrels
- Fried Eggs can now be found in Chests in Fletcher Buildings in Villages
- Frozen Apples and Ice Cream Buckets can now be found in both Igloo Chests and Ice Box Chests in Ancient Cities
- Sniffers can now find Chorus Flowers and Chorus Carrots in the End dimension
- Enchanted Golden Chorus Fruit is now rarer
Bug Fixes
- Pack file name displays version 0.1.0 for version 1.0.0
- The fishing loot table doesn't work when being run as a product of the /loot command
- Wandering Traders do not receive random names
- Custom mobs do not have names set, so death messages when killed by them are incorrect
- Some custom recipes are in incorrect categories, or not in a category
- Remnant files exist, from Vanillabean's development, that have gone unused
- The wiki has a few typos
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:LEcw1HH7:xw6ILSTx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LEcw1HH7:xw6ILSTx"
}

