Welcome to Growthcraft. Growthcraft is a collection of Minecraft mods that adds an extra layer of immersion into the world of Minecraft. Growthcraft adds apple trees, honey, hops, grapes that grow along rope, cheese, yogurt, ice cream, butter, rice, ale, wine, juice, cider, kumis, and sake. Many drinks can also be aged or fermented further for stronger effects.
There are multiple starting points to Growthcraft. The in-game manual is the primary gameplay reference for Growthcraft 1.21.1 and includes getting started notes, recipes, machine guidance, and release information.
This project uses the NeoForge ModDev plugin. IntelliJ run configurations are generated by the genIntellijRuns task, not by the standard Gradle createLaunchScripts task (which belongs to the Application plugin and creates OS launch scripts, not IDE configs).
- Generate IDEA run configs:
./gradlew genIntellijRuns - As a convenience, you can also run:
./gradlew createLaunchScripts(alias togenIntellijRunsin this repo) - VS Code users can run:
./gradlew genVSCodeRuns
After generation, reload the Gradle project in IntelliJ if run configs do not appear immediately.
End of Support: TBD
Latest Version: 1.21.1.8
Stable Version: 1.21.1.8
End of Support: TBD
Latest Version: 9.2.0
Stable Version: 9.2.0
End of Support: 6/9/2023
Latest Version: 8.1.0
Stable Version: 8.1.0
End of Support: Never Released
Latest Version: 7.0.0 (TBD)
Stable Version: TBD
Going from Minecraft Forge 1.12 to 1.16 made a lot of changes to the MCP mappings to the point that it prompted a complete rewrite from the ground.
End of Support: 31 DEC 2023
Latest Version: 6.1.4
Stable Version: 6.1.4
End of Support: TBD
Latest Version: 4.2.2.1
Stable Version: 4.2.2.1
Note: Growthcraft 4 remains supported thanks to ongoing maintenance by Doenerstyle.
End of Support: 11 AUG 2018
Latest Version: 2.7.2
Stable Version: 2.7.2
Growthcraft 2 was a major re-release of Gwafu's original work. In 2015, the Growthcraft "Community Edition" Team was given permission to take over the mod development.
In this version, we added village structures and two additional submodules: Growthcraft Milk and Growthcraft Rice. These mods added cheese, yogurt, ice cream, sake, rice, and thistle crops. When we first rolled out the thistle crop, it was known to wildly grow and take over entire worlds.
End of Support: 13 JUL 2014
Latest Version: 2.1.0a
Stable Version: 2.1.0a
The original Growthcraft mod was created and developed by Gwafu. He did a lot of improving it over a period of three years.
The development branch is protected and should only be updated through pull requests.
Before starting code changes:
- Confirm the working tree is clean with
git status. - Update the local base branch with
git checkout developmentandgit pull. - Create a scoped branch for the work instead of committing directly to
development.
Use one of the project branch roots with an issue-oriented branch name:
feature/<issue-number>-short-descriptionfor additive work.bugfix/<issue-number>-short-descriptionfor fixes.chore/<issue-number>-short-descriptionfor maintenance-only changes.
Open pull requests back into development, link the relevant issue, and include the verification performed before
requesting review.
Growthcraft registers growthcraft:config_value for NeoForge recipe conditions. Use it in neoforge:conditions with a
module and dotted config name when a recipe should load only if a Growthcraft boolean config value is enabled.
Supported modules in the 1.21 port are core/growthcraft, cellar/growthcraft_cellar, and
milk/growthcraft_milk. Unknown modules, unknown paths, and non-boolean values fail closed and log a diagnostic.
We maintain the mod_version in gradle.properties using a Minecraft-version-prefixed scheme (e.g., 1.21.1.x). Whenever a significant feature or behavior change is completed (for example, the Rope block implementation), increment the version:
- Update mod_version in gradle.properties.
- Update the version badge at the top of README.md and the History section's Latest/Stable lines.
- Include the version bump in the same PR as the feature or immediately after.
Use patch-level bumps (the final number) for additive features, fixes, and small changes. Consider minor/major schema changes if we later adopt broader semver rules.