Its like a normal vein miner but in Minecraft's settings it allows you to config the vein miner to vein mine ANY block of choice including modded blocks.
I’ll build a Fabric 26.2 vein-miner mod from scratch with:
JSON configuration for any namespaced block ID, vein size, radius, and sneak-only behavior.
Server-side vein traversal that supports vanilla and modded blocks.
A block-break mixin that triggers the traversal safely after the origin block breaks.
A keybind and client config screen so the feature can be adjusted from Minecraft’s settings flow.
Created a Fabric 26.2 vein-miner mod from scratch.
Features:
Supports any registered vanilla or modded block via namespaced IDs such as
minecraft:stoneormod:block.Config stored at
config/veinminer.json.Configurable maximum vein size and search radius.
Optional sneak requirement.
Server-side connected-block traversal with recursion protection.
Preserves normal block-breaking behavior and drops.
Vkey opens the in-game configuration screen.Keybind appears under the Vein Miner controls category.
Uses Java 25, official 26.2 names, split client source sets, and Fabric API 0.158.0+26.2.
The compilation failed with this error:
[FABRIC] Compiling 6 Java files for MC 26.2 (release 25)
[ERROR] Compilation failed
/workspace/src/main/java/client/java/com/kodari/veinminer/client/VeinMinerClient.java:7: error: package net.fabricmc.fabric.api.client.keybinding.v1 does not exist
import net.fabricmc.fabric.api.client.keybinding.v1.KeyMappingHelper;
^
1 error
Please fix this error by creating a new artifact with the corrected code.
Replace the outdated
keybindingpackage with Fabric 26.2’skeymappingpackage.Keep the existing key registration and configuration-screen behavior unchanged.
Fixed the compilation error by updating the import to the Fabric 26.2 package:
import net.fabricmc.fabric.api.client.keymapping.v1.KeyMappingHelper;
The corrected artifact is ready for compilation.
now import this into a file i can import into my modrinth instance
I can’t generate the binary .jar directly in this environment because the Gradle build tool is unavailable and the project currently contains source files only.
To create the file for your Modrinth instance:
./gradlew build
The compiled mod will be located at:
build/libs/veinminer-1.0.0.jar
Then open your Modrinth instance, select Content → Mods → Add content, and choose that .jar file. Ensure the instance uses Minecraft 26.2, Fabric Loader 0.19.3+, and Java 25.
Ok, give me the file
I can’t provide a usable Modrinth .jar here: this workspace has no compiled artifact, Gradle, Java compiler, or source files available to build one.
A Modrinth instance requires the compiled file:
build/libs/veinminer-1.0.0.jar
You’ll need to build the complete project locally with Java 25 and Gradle:
./gradlew build
Then import the resulting JAR from build/libs/ into Modrinth.
give me my mod
Recreate the missing source files for the Vein Miner mod.
Include the corrected Fabric 26.2 key-mapping import and a buildable client/server split.
Add the packaged mod metadata and configuration resources so the project can produce the Modrinth-ready JAR.
The Vein Miner source has been restored, including the corrected Fabric 26.2 key-mapping import and client/server files.
A compiled .jar is not available in this workspace because Gradle and Java are unavailable, so I can’t attach a Modrinth-importable binary directly. Build the project with Java 25 using:
./gradlew build
The mod file will be generated at:
build/libs/veinminer-1.0.0.jar
Import that JAR into your Modrinth instance.
package com.kodari.veinminer;
import net.fabricmc.api.ModInitializer;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
public final class VeinMiner implements ModInitializer {
public static final String MOD_ID = "veinminer";
public static final Logger LOGGER = LoggerFactory.getLogger(MOD_ID);
@Override
public void onInitialize() {
ConfigManager.load();
VeinMinerService.register();
}
}