Creators
Details
All versions
0.2.0
Beta
0.2.03 years ago 89
Compatibility
Minecraft: Java Edition
1.7.10
Platform
Forge
Supported environments
Client and server
Changes
Originally released on May 17, 2016.
- Add Basin (closes #14)
- Formalize piston crafting and add fluid input/output support
- Fluid inputs must be displaced by the piston head
- Fluid outputs get deposited in the fluid handler block below the piston head (fluid handler below the piston head is required for the crafting to work)
- Add vegetable oil piston crafting recipe (closes #3)
- Add plant milk piston crafting recipe (closes #4)
- Add piston crafting NEI handler
- Add piston crafting recipes for VO inks/soap solution/lye
- Add piston crafting recipes for various HarvestCraft items
- Adds recipes for: Mashed potatoes, batter, dough, and all fruit juices
- Add seitan as a raw meat/cooked meat substitute
- Contributes towards #40
- Add jute seeds as an alternate large fern propagation method
- A Jute Stalk in a crafting grid gives Jute Seeds
- Jute seeds can be planted on dirt/grass/farmland and will grow and eventually turn into a Large Fern
- Closes #39
- Add leather armor oredict entries.
- Fix smelting various VO items not giving XP
- Fix cross-mod exploit with Pam's HarvestCraft's Fresh Milk VO would convert Milk -> 4x Fresh Milk recipe into the oredict version (to allow Plant Milk to be used instead), but Fresh Milk is included in the oredict so it'd create a Fresh Milk -> 4x Fresh Milk recipe
- Fix ender rifts crashing in certain dimensions
- Fixes #53
- Skip redundant milk_bucket OreDict entry when MFR is installed
- Could cause problems, see for example http://pastebin.com/ujPCTxiF
- Make Soap only cure potion effects that Milk does
- Fixes soap clearing potion effects that should be incurable (e.g. Thaumcraft warp)
- Fixes #50 and part of #18
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:H56rRCo3:cgfvgCgD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:H56rRCo3:cgfvgCgD"
}

