
Handwerk – AoE Tools, Vein Miner, Ore Variants & Building Blocks
Vanilla-style tools that do the work for you: AoE hammer & shovel, vein miner, tree feller, harvester scythe. Plus tool upgrades, magnet enchantments, ores in their host rock & a building palette — slabs, stairs, trapdoors, lanterns, redstone chains.
Tags
Creators
Details
0.16.1-26.1.2+build.10-neoforge
Compatibility
Required content
Changes
Handwerk 0.16.1 — MidnightLib optional, 26.3 snapshots
✨ New
- MidnightLib is optional. It is only needed for the config screen — without it Handwerk runs on its defaults.
- Snapshot builds for Minecraft 26.3, marked alpha.
- A warning when the installed Ohmega version can lose items put into an accessory slot. Ohmega 1.6.0-beta.18 is affected in freshly created worlds; leaving and re-entering the world avoids it, and beta.19 fixes it.
🩹 Fixes & tweaks
- Sneak + right-click with a shovel turned any block into dirt. Only paths revert now. This affects every supported version.
- Copper lanterns and redstone chains carried a broken serialisation entry. Nothing in normal play used it.
⚙️ Technical
- Toolchain: Gradle 9.7.0, Fabric Loom 1.17.19, Stonecutter 0.9.7. Kotlin stays on 2.4.10.
🧪 Testing
I could not test this release thoroughly, and I would rather say so than pretend otherwise. Only the 26.3 build was played through case by case. On 26.2 (Fabric and NeoForge) and on 1.21.x I started the game and checked the areas I had touched — accessory slots and the Lodestar Charm's magnet — and nothing else. 26.1.2 was built and left at that. This is a matter of time, not of confidence: going through five targets by hand takes longer than I have.
The test protocol is public and lists every case. If you play Handwerk on 1.21.x, 26.1 or 26.2, findings are very welcome — the shovel bug above came out of exactly one such pass.
Optional dependencies
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:AcxzUn56:WOex7lRj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AcxzUn56:WOex7lRj"
}
