
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.15.4-26.1.2+build.2
Compatibility
Required content
Changes
Handwerk 0.15.4 — NeoForge
Handwerk now runs natively on NeoForge, alongside its existing Fabric builds — no Sinytra or Connector required. This release also polishes a few things that every build benefits from.
✨ New
- Native NeoForge support for Minecraft 26.1 and 26.2. It's a first-class jar, tested to play exactly like the Fabric version. (The 1.21.x line stays Fabric-only.)
🩹 Fixes & tweaks
- The Lodestar Charm gets a proper accessory slot again. With Trinkets (and its forks) a necklace slot now shows up for the charm — previously none ever appeared. It also works with Ohmega on every version now.
- The Harvester Scythe clears sugar cane, bamboo and cactus across its whole area again, not just the single stalk you click.
- Hanging redstone lanterns render correctly. The hanging variants were there but showed the wrong model.
- Redstone lanterns and redstone chains moved to the Redstone tab. They now sit next to the redstone lamp in the creative menu instead of with the plain lanterns and chains. (Plain lanterns still live with the vanilla lantern.)
- The VeinBlocks Amount setting takes effect immediately instead of only after a restart.
- The Enable Shovel Path Toggle config option is respected again — turning it off previously did nothing.
🧪 Testers welcome
This is Handwerk's first NeoForge release, so extra hands are appreciated. Handwerk now ships a full test protocol — a version- and loader-aware checklist covering every feature, with the exact in-game commands and expected results (docs/Handwerk-Test-Protocol.ods in the repository). If you'd like to help verify builds — especially the new NeoForge ones — run through it on your setup and share the results on Discord.
⚙️ Technical
- Multi-loader architecture. All loader-specific runtime code now sits behind an internal platform layer. The NeoForge jar re-packages the same compiled game code (26.x is unobfuscated) with NeoForge entrypoints, data maps for copper oxidation, and an access transformer.
- Removed a few stray Ohmega files the 26.1 build had accidentally bundled during development, which could otherwise shadow Ohmega's own files.
- Loosened the version bounds on the suggested companion mods (Sodium, Iris, Mod Menu); the old bounds pointed at outdated 1.21.4-era versions.
- Dependency refresh: Fabric API 0.155.2 (26.x) / 0.141.5 (1.21.11) and Kotlin 2.4.10 — Fabric Language Kotlin ≥ 1.13.13 is now required (your launcher updates this automatically). NeoForge builds use Kotlin for Forge.
💬 Feedback and bug reports are very welcome — join us on Discord. Thanks for playing! ⚒️
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:dvjzLAOP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AcxzUn56:dvjzLAOP"
}
