
NPC Logistics
Adds Logistics Worker NPCs that execute item-collection and delivery routes across chests and barrels, run automated crafting pipelines, and now take on autonomous Roles — starting with a fully functional Farmer who tills, plants, harvests, and restocks.
Links
Tags
Creators
Details
1.1.6
Compatibility
Changes
What's new in 1.1.6
New roles
- Dairy Worker (equip a Bucket) — milks cows, manages a bucket economy: takes empty buckets from the deposit chest, returns milk buckets after each round. Auto-tags nearby cows on activation.
- Chicken Collector (equip a Feather) — scans for naturally dropped eggs near the jobsite and deposits them to the chest.
Livestock system
- Per-herd collar colours — each NPC worker gets a unique ring colour
derived from their identity. Dave's flock and Jones's flock are visually
distinct when viewed through Work Goggles. - Charged Livestock Tags — right-click an NPC worker with an unstamped
tag to charge it with that worker's herd colour. Animals you tag manually
will then match the worker's ring colour. - Untag gesture — sneak + right-click a tagged animal with an empty hand to release it.
- Collar rings gated behind Work Goggles — rings are now only visible
while wearing Work Goggles (previously always visible). - Stray threshold tightened — animals are nudged back at 20 blocks from their pen (was 32).
- Tagging restricted — manual and auto-tagging now applies to sheep,
cows, pigs, and chickens only (rabbits were accidentally included before).
Pathfinding
- Workers no longer route over chest or barrel lids mid-path. A custom
navigation layer marks chest/barrel tops as obstacles so workers walk around them naturally.
Shepherd
- No-gate fallback — if no fence gate is found near the jobsite, the
shepherd operates free-range and navigates directly to the jobsite centre
instead of stalling.
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:ZI1FwCX7:b4hI5mWL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZI1FwCX7:b4hI5mWL"
}
