Links
Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 2 months ago
Updated last week
All versions
1.4.1+26.2
Release
DG: Natural Reproduction 1.4.1+26.22 months ago 3
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client-side
Server-side
Changes
Added
- Pasture Enrichment, Rotational Grazing & Feeding Trough Dynamics: Implemented complete pasture enrichment and overgrazing mechanics using strictly vanilla interactive blocks and native particle effects:
- Multi-Structure Pasture Enrichment: Automatically detects vanilla feeding troughs (water cauldrons, composters with compost/crops), hay reserves (
Blocks.HAY_BLOCK), natural water sources, and barn ceiling weather shelters within 16 blocks. - Well-Nourished Livestock State: Living in enriched pastures grants herds +25% faster autonomous breeding check intervals, +10% offspring scale recovery (up to 1.30x max), and periodic golden
ParticleTypes.WAX_ONsparkle particles. - Dynamic Overgrazing Terrain Wear: Dense herds (5+ animals in an 8-block area) grazing without pasture rotation dynamically convert grass blocks into
Blocks.DIRT(orBlocks.COARSE_DIRTfor 8+ crowding), requiring pasture rotation to keep foraging grounds fertile.
- Multi-Structure Pasture Enrichment: Automatically detects vanilla feeding troughs (water cauldrons, composters with compost/crops), hay reserves (
- AnimalPastureHelper: Created single-purpose helper class managing pasture enrichment evaluation, overhead barn shelter scanning, overgrazing wear, and well-nourished sparkle effects.
- Dedicated GameRules: Registered
natural-reproduction:pasture_enrichment(Boolean, defaulttrue) andnatural-reproduction:overgrazing(Boolean, defaulttrue), integrated into/gamerule,/naturalreproductioncommand suite, and YACL screen.
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:WT4xq2BM:tQ7nHTvY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WT4xq2BM:tQ7nHTvY"
}

