All versions
1.2.1
Release
MechWorks 1.2.1last month 84
Compatibility
Minecraft: Java Edition
1.20.1–1.20.6
Platform
Fabric
Supported environments
Client and server
Changes
1.2.1
Pack-maker and server-compatibility release — no gameplay changes, all about giving modpacks and servers control.
For Pack Makers & Servers
- Extensive config: bot mining speed, dig speed, and energy costs
(
botMineCooldownTicks,botDigCooldownTicks,botMineEnergyCost,botDigEnergyCost); flattener throughput (flattenBlocksPerPass); mech fuel consumption (the existingenergyDrainMultiplierapplies to every mech energy cost) — all inconfig/mechworks.json, which auto-regenerates with new fields on update. - Block blacklists: blocks in the
mechworks:bot_unbreakableblock tag or thebotBlockBlacklistconfig list are never broken or replaced by any bot — dig routes plan around them. - Claim protection awareness (
botsRespectClaims, default on): bots carry their deployer's identity and clear every block edit through the standard Fabric protection events, so chunk-claim mods (FTB Chunks, Open Parties and Claims, and similar) see the owner at work — bots mine their owner's claims and refuse everyone else's. Ownerless bots are adopted by the first player to interact with them. - Item-pipe interop: the Charging Chest exposes the Fabric transfer API, so modded pipes and conduits can insert and extract (vanilla hoppers already worked).
- Recipes: audited — every craftable item and block ships as a plain
JSON recipe under
data/mechworks/recipes/, overridable by datapack for progression gating. - On energy: MechWorks speaks Team Reborn Energy, the Fabric ecosystem's shared energy standard (the FE-equivalent on this loader); Tech Reborn, Modern Industrialization, and friends interoperate through it out of the box.
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:UyaOyiEx:r6n2nVIt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UyaOyiEx:r6n2nVIt"
}

