0.7.7
Compatibility
Changes
Molten Veins 0.7.7
No new toys this time. I went bug hunting instead, and found more than I expected. Everything below is fixed on both Fabric and NeoForge, on every supported version.
Minecraft: 1.21.8 · 1.21.9 · 1.21.10 · 1.21.11 · 26.1 · 26.1.1 · 26.1.2 · 26.2
🧰 The big ones
📦 Your chests are safe now
This was the worst one. Tunnel, Hammer and Layer mode would happily chew through any chest, barrel, shulker box or furnace that got caught in the area, and everything inside went with it. Those modes now leave storage blocks alone. If you've lost a base chest to a Layer break, sorry about that. It won't happen again.
🎚️ Your toggles actually work everywhere
Switching an ore off in the settings only did anything in Vein mode. Excavate, Tunnel, Hammer and Layer just ignored you and mined it anyway. All five modes respect your per-block toggles now.
🔢 Your Mining Limit actually works everywhere
Same story. Tunnel and Layer never looked at the Mining Limit, only at their own sliders, so a Layer at radius 16 tore out 1089 blocks no matter what you set the limit to. The Mining Limit is now the real cap for every mode. Layer also grows outward in rings, so when the limit does trim it you get a neat area centred on where you dug instead of a lopsided corner.
💎 Silk Touch dupe, patched
With Silk Touch equipped, the extra blocks were being handed a made up copy of the block item instead of what the block actually drops. That turned spawners, budding amethyst and reinforced deepslate into farmable items, and gave you the wrong thing for slabs, snow layers and crops. Silk Touch now goes through the real loot table like it should.
🛡️ Claims and protected land are respected
On NeoForge the mod kept going even when a claim or spawn protection mod had already blocked the break, so the block you hit stayed put while the rest of the vein quietly disappeared. It now stops when a break gets blocked, and it checks build permission on every extra block before touching it. Both loaders.
💥 Crash fix on modded ores
Certain modded blocks could make the ore check throw, which turned a plain block break into a crash. That's guarded now. Vanilla blocks also can't get mistaken for modded ores anymore, even if a data pack renames them.
🔧 Smaller stuff
Broken pickaxe, free block. When your tool snapped mid vein, the mod snuck in one more break and dropped it without any XP. Mining stops when your tool breaks now, like it should.
Clay and Fortune. Auto smelted clay was getting multiplied by Fortune, so Fortune III could turn 4 bricks into 16. Vanilla clay doesn't care about Fortune, and now neither do we.
Config file safety. Saves go through a temp file first, so a crash or an unlucky double save can't leave you with a half written config. A broken config file now falls back to defaults instead of blowing up while you're mining.
Memory leak. Player mining state was never cleaned up on disconnect, and every activation that found nothing to break left a little junk behind. Long running servers stay tidy now.
📥 Grab the right jar
| Minecraft | Fabric | NeoForge |
|---|---|---|
| 1.21.8 | moltenveins-0.7.7-mc1.21.8.jar |
moltenveins-neoforge-0.7.7-mc1.21.8.jar |
| 1.21.9 | moltenveins-0.7.7-mc1.21.9.jar |
moltenveins-neoforge-0.7.7-mc1.21.9.jar |
| 1.21.10 | moltenveins-0.7.7-mc1.21.10.jar |
moltenveins-neoforge-0.7.7-mc1.21.10.jar |
| 1.21.11 | moltenveins-0.7.7-mc1.21.11.jar |
moltenveins-neoforge-0.7.7-mc1.21.11.jar |
| 26.1 / 26.1.1 / 26.1.2 | moltenveins-0.7.7-mc26.1-26.1.1-26.1.2.jar |
moltenveins-neoforge-0.7.7-mc26.1-26.1.1-26.1.2.jar |
| 26.2 | moltenveins-0.7.7-mc26.2.jar |
moltenveins-neoforge-0.7.7-mc26.2.jar |
Fabric: Fabric Loader + Fabric API NeoForge: the matching NeoForge version Java: 21 for the 1.21.x jars, 25 for the 26.x jars
Your existing config/moltenveins.json carries straight over. Nothing to redo.
Found something broken? Come tell me about it.
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:XvxD0SDK:HqcIKaQN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XvxD0SDK:HqcIKaQN"
}

