Tags
Creators
Details
Licensed GPL-3.0-only
Published 3 years ago
Updated last month
All versions
Note: Repository has moved. Includes
2.0.0
Release
Create: Food 2.0.010 months ago 527
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
*** 2.0.0 ***
Note: Repository has moved. Includes 1.21.1-neoforge, 1.20.1-fabric, and 1.20.1-forge.
Changes:
- 50+ new items.
- Display names are now simplified to be closer to vanilla naming.
- Ingredient and mod compatibility information is now displayed in tooltips. Recommend enable
searchAdvancedTooltipsif using JEI. - New config
createfood-client.toml. Disable items & adjust tooltips to your liking. - Add upright on belt tags. (#86)
- Basic support for Display Delight. (#90)
- Balancing changes for cake recipes. (#91)
- Pumpkin pie, cheese block, and all frosted cakes are now placeable & sliceable.
- Standardize some fluid amounts.
- Adjust saturation for some biscuit sandwiches.
- Add composting for various items.
- Various minor texture updates.
- Cakes are no longer stackable to match vanilla behavior.
- Changed IDs:
raw_chorus_cookie->raw_chorus_fruit_cookieraw_sweet_berry_cookie->raw_berry_cookie
- Removed items:
mutton_wrap_onion_lettuce_tomatomutton_wrap_onion_tomato
Fixes:
- Fix chicken patty recipe. (#79)
- Fix missing melon jam filling recipe. (#85)
- Fix cotton candy stick mixing recipe. (#92)
- Fix cloth filter recipe. (#95)
- Fix crashes/errors related to tomato sauce filling recipes. (#96)
- Fix gelatin dessert block cutting recipe.
- Fix some emptying recipes using old fabric amounts.
- Fix cream cake textures having incorrect sides.
- Fix missing cooking recipes for pumpkin pie.
- Fix some missing saturation values.
- Fix some item application & deploying recipes not having remainder items.
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:4HnO3el1:7AGKMTam"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4HnO3el1:7AGKMTam"
}

