Links
Tags
Creators
Details
Licensed CC0-1.0
Published last year
Updated last year
All versions
1.3.0
Release
Auto Replanter 1.3.0last year 72
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Any compatible version
Changes
[1.3.0] - 2025-08-12
Added
- Custom Block Replacement System: New feature allowing automatic replacement of non-crop blocks with other blocks when harvested
- Configure custom replacement rules in
customBlockReplacementsarray - Each rule specifies target block, replacement block, and individual tool damage settings
- Perfect for modded blocks like mushroom colonies that should replant when harvested
- Works independently of crop blocks and respects all existing configuration options
- Configure custom replacement rules in
- New configuration option
useCustomBlockReplacementsto enable/disable the feature - Default configuration includes Farmer's Delight mushroom colony replacements:
- Brown mushroom colonies → Brown mushrooms
- Red mushroom colonies → Red mushrooms
Enhanced
- Improved block processing logic to handle both crops and custom block replacements efficiently
- Enhanced tool damage system with per-block damage control for custom replacements
- Expanded loot processing to work with any block type, not just crops
Technical Changes
- Added
CustomBlockReplacementEntryhelper class for optimized block lookup - Implemented custom replacement map for fast block ID to replacement mapping
- Refactored block breaking logic into modular methods for better maintainability
- Added comprehensive JavaDoc documentation for new methods
Configuration
- Added
customBlockReplacementsarray with structure:{ "target": "block:id", "replacement": "replacement:block", "damageTool": true/false } - Added
useCustomBlockReplacementsboolean option (default:true)
Compatibility
- Fully compatible with existing crop replanting functionality
- Works with any modded blocks that have valid block IDs
- Respects all existing configuration options (tool requirements, sneak mode, etc.)
- No breaking changes to existing configuration files
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:Xn2nBuhS:meNw00RO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Xn2nBuhS:meNw00RO"
}

