All versions
1.1.0
Release
Utility Golems 1.1.04 days ago 20
Uploaded by
Compatibility
Minecraft: Java Edition
1.20.1–1.20.6
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Changes
Added
- Charcoal Golem: right-click it with a stick to light it into a torch.
- Mud / Hay Golems: once one of these golems finds real farmland while doing its normal work (harvesting/planting/bonemealing), it now tethers more tightly to that farm instead of just its distant chest, so it stays close to the crops it's actually tending. If that farmland is later broken or replaced, the tighter tether is released automatically and the golem falls back to its normal chest-based range instead of getting stuck.
Fixed
- Timber / Charcoal / Mud Golems: fixed a bug where interacting with a single chest permanently restricted the golem's entire search-and-wander range to a tiny 4-block radius around that chest, regardless of each goal's own much larger search range. The chest tether radius has been increased from 4 to 48 blocks, so Timber Golems keep finding trees, Charcoal Golems keep collecting/planting saplings and clearing flowers, and Mud Golems keep harvesting crops well beyond their starting chest - all without needing a fence to contain them.
- Hay Golem: fixed a bug where it would roam freely instead of staying near its chest. It now tethers to the first chest it interacts with (via seed/bonemeal collection).
- Timber Golem: extended its reach so it can consistently reach and start chopping tree trunks (was too short for some Spruce trees).
- Charcoal Golem: fixed a bug where it could get stuck staring at an unreachable sapling item indefinitely, repeatedly retrying the same item instead of moving on to other work. Charcoal golems also now prioritize collecting and planting saplings over breaking flowers.
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:z1kkndBE:4OV9zCqU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:z1kkndBE:4OV9zCqU"
}

