All versions
1.9.4
Release
Orevein 1.9.44 months ago 108
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Client-side
Changes
[1.9.4] - 2026-05-19 (Minecraft 26.1.2)
fabric/build/libs/orevein-fabric-1.9.4-V26.1.2.jar 2e9685508cf7efc0573c8232071c22e8e72693595331820dc0034a5eca6fc8a6
Added
- Vein Harvest — Sneak + break a fully-grown crop while holding a netherite hoe to harvest the entire connected crop patch in one swing. Crops auto-replant in place (no dropped seeds). Configurable via
enableVeinHarvestandmaxVeinSizeCropsinorevein.json. - Mass Till — Sneak + right-click dirt or grass while holding a netherite hoe to till a 3×3 area (scales to 5×5 in 5×5 tunnel mode, or matches your Custom Size selection). Configurable via
enableMassTill. - OreVein HUD widget — Compact on-screen status overlay showing your current mode and XP. Toggle it with the new "Toggle OreVein HUD" keybind (unbound by default, set it in Minecraft's Controls screen).
Changed
- XP unlock thresholds are now server-synced. The radial menu previously showed hardcoded client-side threshold values; it now receives the actual thresholds from the server on join. Modpacks that customise
tunnel1x2UnlockXP,tunnel3x3UnlockXP,tunnel5x5UnlockXP, orcustomSizeUnlockXPinorevein.jsonwill now display the correct requirements in the UI.
Fixed
- Fabric install broken for some users/launchers. The Fabric jar was bundling fabric-api with a broken Jar-in-Jar reference (pointed to a single monolithic jar that never existed in the archive). Launchers that inspect nested JiJ metadata could misidentify the mod or fail to satisfy the fabric-api dependency. The bundling is now generated correctly at build time.
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:fsZC35ec:6HtLwXen"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fsZC35ec:6HtLwXen"
}

