Tags
Creators
Details
Licensed MIT
Published 4 months ago
Updated 3 weeks ago
All versions
0.23.0+26.2-neoforge
Release
Forget-Me-Crops 0.23.0+26.2-neoforge3 weeks ago 21
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Required content
Any compatible version
Changes
0.23.0
- Fix
mendingProtectionnever taking effect: hoe enchantments are now read through the level enchantment registry instead of a reflective lookup that returned no results on current Minecraft versions, so Mending (and Unbreaking) on a framed hoe is detected again. - Add shared
HoeUtilsenchantment-level helpers for Silk Touch, Fortune, Unbreaking, and Mending. - Fix seed reserves being stranded outside the anchor chest: reserve-tracked seed and crop-fruit drops are now inserted into the chest directly under the item frame before any nearby extra storage, so replanting can draw on them when a second chest is present.
- Update README and TECHNICAL docs to describe anchor-chest-first seed routing and registry-backed enchantment lookup.
- Publish only the newest
CHANGELOG.mdversion section as the Modrinth and CurseForge release notes instead of the entire file. - Extend release notes to span every
CHANGELOG.mdversion section newer than the release already live on Modrinth, so multiplemod_versionbumps between publishes are all reported. - Resolve the last published version from the public Modrinth version list, falling back to the newest changelog section when the lookup is unavailable.
- Add
printReleaseChangelogto preview the release notes without publishing. - Correct the documented publish task name to
chiseledPublishAll. - Align the build and governance tooling with the MinersAdvantage repository so both projects behave identically.
- Adopt the stricter version-bump validator, which now requires a
Next Versionentry in the bump state and an override file for same-day re-bumps. - Add a full test-suite gate to the pre-commit hook, backed by new
validate-test-suiteandrun-gradle-java25scripts. - Reject placeholder version-bump entries during changelog validation.
- Add
publishPreflightandpublishPostSummaryreporting around publish tasks, plus a no-oppublishModsfallback when no tokens are configured. - Register
chiseledPublishAllPublicationsToLocalRepositoryand the GitHub Packages equivalent so the release workflow resolves the tasks it invokes. - Correct the release workflow to call
chiseledPublishAllinstead of the non-existentchiseledPublishMods. - Add
AGENTS.mddescribing the repository workflow rules for coding agents. - Add the shared optimization-rebuild prompt and commit-outstanding-semantic skill under
.github/. - List the full validator set and pre-commit ordering in TECHNICAL.
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:7YR2UVAs:RHUQEOtP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7YR2UVAs:RHUQEOtP"
}

