0.8.3
Compatibility
Changes
Molten Veins 0.8.3
NeoForge 26.3 has gone stable, so the 26.3 NeoForge build is off the betas and onto the real release. I also fixed a handful of bugs, including one that was handing out far too much netherite.
Minecraft: 1.21.8, 1.21.9, 1.21.10, 1.21.11, 26.1, 26.1.1, 26.1.2, 26.2, 26.3 Loaders: Fabric and NeoForge
NeoForge 26.3 is now on the stable release
0.8.2 had to sit on 26.3.0.52-beta, because the betas after it crashed on the title screen.
NeoForge has fixed that since, and 26.3 now has proper stable releases. The first one was
26.3.0.76, so that is what this is built against.
The 26.3 NeoForge jar needs 26.3.0.76 or newer. It works on every stable 26.3 build from
there up, including the newest one out right now. I checked everything Molten Veins uses from
NeoForge in both the oldest and newest stable builds, and none of it changed between them.
If you are still on a 26.3 beta, update NeoForge to the latest stable. You no longer need to
avoid .53 through .55, because there is no reason to be on a beta at all now.
Fixes
Fortune was multiplying Ancient Debris. This is the big one. In vanilla, Fortune does nothing to Ancient Debris, one block always gives you one. With auto-smelt on, Molten Veins was applying Fortune to it anyway, so a Fortune III pickaxe could turn one debris into as many as four netherite scrap. That is a lot of free netherite. It now gives exactly one, same as vanilla. Clay already had this exemption, debris just never got it.
Adding a vanilla block to extraBlocks made it auto-smelt every time you broke it. The
extraBlocks list is meant to let you vein mine extra blocks. But if you put a vanilla block in
there, say minecraft:oak_log for tree felling, the mod also started treating it as a smeltable
ore. So every log came out as charcoal, and sand would come out as glass, even when you just
broke one block normally without the key held. Vanilla blocks in that list now get vein mined
and nothing else. Blocks from other mods are unaffected.
Gem-style modded ores gave no XP. Ores from other mods that drop a gem rather than a raw ore keep their XP in the block itself, not in a smelting recipe, and because Molten Veins breaks blocks its own way, that XP was getting skipped entirely. You would mine a vein of some modded gem ore and get nothing. They now pay out their XP like they should, on both loaders, and Silk Touch still correctly gives none.
Hammer mode dug the wrong way when you looked down at the floor. Hammer mode picked which way to lay its 3x3 based on where you were looking, not which face of the block you actually hit. So mining a floor block a couple of blocks in front of you, looking down at a shallow angle, dug a vertical 3x3 into the ground instead of clearing a flat patch of floor. It now follows the face you hit.
A long extraBlocks list could stop vein mining working on servers. Your settings get sent
to the server, and the two block lists were being sent along with them even though the server
always uses its own lists instead. In a big modpack with a long extraBlocks list, that could
push the message past its size limit, and once that happened your settings and keys stopped
reaching the server at all. The lists are no longer sent, so it stays small no matter what is
in them.
Which jar do I want
| Minecraft | Fabric | NeoForge |
|---|---|---|
| 1.21.8 | moltenveins-0.8.3-mc1.21.8.jar |
moltenveins-neoforge-0.8.3-mc1.21.8.jar |
| 1.21.9 | moltenveins-0.8.3-mc1.21.9.jar |
moltenveins-neoforge-0.8.3-mc1.21.9.jar |
| 1.21.10 | moltenveins-0.8.3-mc1.21.10.jar |
moltenveins-neoforge-0.8.3-mc1.21.10.jar |
| 1.21.11 | moltenveins-0.8.3-mc1.21.11.jar |
moltenveins-neoforge-0.8.3-mc1.21.11.jar |
| 26.1 / 26.1.1 / 26.1.2 | moltenveins-0.8.3-mc26.1-26.1.1-26.1.2.jar |
moltenveins-neoforge-0.8.3-mc26.1-26.1.1-26.1.2.jar |
| 26.2 | moltenveins-0.8.3-mc26.2.jar |
moltenveins-neoforge-0.8.3-mc26.2.jar |
| 26.3 | moltenveins-0.8.3-mc26.3.jar |
moltenveins-neoforge-0.8.3-mc26.3.jar |
Grab the one matching your version and your loader, drop it in mods, done.
Fabric: Fabric Loader plus Fabric API. NeoForge: the matching NeoForge version, and
26.3.0.76 or newer if you are on 26.3.
Java: 21 for the 1.21.x jars, 25 for the 26.x jars.
Your config carries straight over and no settings changed this release.
Found something broken? Come tell me, I'd genuinely rather know.
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:WasgYwtD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XvxD0SDK:WasgYwtD"
}

