1.1.0
Compatibility
Changes
1.1.0 — The Collector
A seventh job joins the crew. Hand a golem a Collector Work Order (bundle centerpiece), tap a chest as its bank, and it gathers everything "ready to collect" around it:
- Ripe produce — sweet berries, glow berries, cocoa, melons & pumpkins (only fruit grown by an attached stem, so decorative builds are safe), amethyst clusters (only on budding amethyst), sugar cane, cactus, bamboo.
- Furnace output — during the bind, tap furnaces / smokers / blast furnaces to enrol them; the golem drains their result slots into the bank. It never touches a furnace you didn't tap.
- Ground sweep — reclaims its own families' drops (bamboo pops, harvest overflow).
- The 9-slot filter (sneak + matching Work Order) picks which products it collects — naming the block or the item both work (MELON counts as melon slices).
- Per-family toggles, scan radius, and vertical range under
collector:inconfig.yml.
Every harvest is loot-table or real-slot based — nothing is minted, nothing voided, and no block a player placed is ever broken.
Also in this release (all jobs):
- Re-tasking a golem mid-haul now drops its cargo instead of destroying it.
- The anti-dupe hand-wipe now drops instead of deleting held items (protects real items under
suppress-native-sort: off). - Golems wake when a player is near their Sorter destinations or enrolled workstations, not just the source/dest.
- Work Order items render proper names even if your
messages.ymlpredates this version (new keys carry baked-in fallbacks — merge the new keys, or deletemessages.ymlto regenerate, for the fully styled copy).
Admin notes:
- New permission node:
workorders.job.collector(defaulttrue). collector.families.bamboorequirescollector.sweep-produce(auto-disabled with a console warning otherwise).- Furnace draining requires physically tapping each furnace during the bind session — the radius scan never opens containers, so there is no way to drain a furnace nobody consented to.
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:7mODBXP2:Fsj8E2XM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7mODBXP2:Fsj8E2XM"
}

