All versions
0.1.3
Release
Mini Workers 0.1.33 months ago 25
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Client and server
Changes
Mini Workers 0.1.3
This update adds fishing automation and improves several worker stations.
Added
- Added the new Fishing Station.
- Added the Fisher Worker.
- The Fisher can find nearby water and fish from a valid shoreline position.
- Added fishing animations, a custom bobber, fishing line, splash effects, and bite/reel behavior.
- Fishing can catch normal fish, junk, and valid open-water treasure.
- Fishing rods now support Lure, Luck of the Sea, and Unbreaking effects.
- Fishing catches are safely stored in the station Output.
- If the Output is full, the catch is held safely until space is available.
Improved
- Redesigned the visuals for Farm, Lumber, Ranch, Mining, Fishing, and Sorting Junction stations.
- Improved the Fishing Station screen, status messages, and activity indicator.
- Ranchers now spawn more consistently with other workers.
- Farm Station New Field mode can now create a new field without needing pre-tilled farmland.
- Farmers can collect useful seeds while clearing vegetation.
- Improved seed handling so new fields keep enough seeds for planting.
Fixed
- Fixed dark side shading when stations were placed directly next to each other.
- Fixed some valid shoreline water not being detected correctly.
- Improved Fishing Station water and path status messages.
- Fixed Fisher movement and action issues near shoreline fishing spots.
- Fixed Fishing Station GUI text overlap.
- Fixed selected farm seeds being sent away before new field creation had enough seeds reserved.
- Fixed Fishing Station Output slots accepting manual item insertion.
- Preserved pending fishing catches during pause, temporary movement issues, or full Output recovery.
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:LKGuEcl1:Q5QJdmOk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LKGuEcl1:Q5QJdmOk"
}

