0.8.1
Compatibility
Changes
Molten Veins 0.8.1
Minecraft 26.3 support, on Fabric and NeoForge both. Also a small fix for the mod lying about its own version number in your log.
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
Minecraft 26.3
Both loaders, tested in game rather than just built. Nothing about how the mod plays has changed, so if you're coming from 26.2 you won't notice a thing except that it runs.
26.3 was more work than a version bump usually is, because Mojang changed two things underneath it.
The first is that they dropped GLFW and moved to SDL for keyboard and mouse input. That's the layer every keybind in the mod sits on, so the Vein Mine key, the V cycle key, the Z menu key and the scroll modifier all had to be rewired. They behave exactly as before and your existing bindings carry over.
The second one actually crashed the game. In 26.3 the method Minecraft calls when a player finishes breaking a block takes different arguments than it used to. Molten Veins hooks that method, because that's how it knows to smelt your ore and start the vein. The catch is that this kind of mismatch compiles perfectly fine and only blows up when you launch, so the jar looked healthy right up until the game refused to start. It's hooked correctly for 26.3 now, and the older versions are untouched.
If you're on NeoForge you'll want 26.3.0.6-beta or newer. Only betas exist for 26.3 so far.
Fixes
The mod was reporting the wrong version in your log. Every launch since 0.7.6 printed this:
Molten Veins v0.7.6 - Auto-smelting and multi-mode mining enabled!
It said that no matter which version you actually had. The number was written directly into the code and I'd been forgetting to update it, so it had been stuck on 0.7.6 for five releases. Harmless in itself, but genuinely annoying if you were reading a log to work out what somebody was running, and it made my own bug reports confusing.
I took the number out instead of correcting it, so it can't go stale again:
Molten Veins loaded - Auto-smelting and multi-mode mining enabled!
Your loader already prints the real version in the mod list at the top of every log, which is the number you can actually trust.
If 26.3 crashes on startup for you
Worth mentioning because it cost me an evening. While testing this release on 26.3 I hit a hard crash at startup, the kind with no crash report and no error message, just the game vanishing.
It turned out to be intermittent. The exact same setup, same mods, same jars, no changes of any kind, later launched perfectly and kept running. When it did crash it picked a different spot each time, and it never once wrote a crash report. That combination of symptoms means it isn't mod code failing, it's something underneath, and 26.3 is the release where Mojang swapped the whole input and window layer over to SDL and started preferring a different graphics backend. My own log shows the game noticing a failed start and falling back to OpenGL on its own.
So if 26.3 dies on you at startup, try simply launching it again before you go pulling your mods folder apart. If it keeps happening, give the instance more memory, make sure your graphics drivers are current, and on a laptop with two GPUs check that Java is being pointed at the real one. 26.3 leans on all of that much harder than 1.21 did.
If it crashes every single time with only Molten Veins installed, that one's on me and I really want to hear about it, ideally with the full log.
Which jar do I want
| Minecraft | Fabric | NeoForge |
|---|---|---|
| 1.21.8 | moltenveins-0.8.1-mc1.21.8.jar |
moltenveins-neoforge-0.8.1-mc1.21.8.jar |
| 1.21.9 | moltenveins-0.8.1-mc1.21.9.jar |
moltenveins-neoforge-0.8.1-mc1.21.9.jar |
| 1.21.10 | moltenveins-0.8.1-mc1.21.10.jar |
moltenveins-neoforge-0.8.1-mc1.21.10.jar |
| 1.21.11 | moltenveins-0.8.1-mc1.21.11.jar |
moltenveins-neoforge-0.8.1-mc1.21.11.jar |
| 26.1 / 26.1.1 / 26.1.2 | moltenveins-0.8.1-mc26.1-26.1.1-26.1.2.jar |
moltenveins-neoforge-0.8.1-mc26.1-26.1.1-26.1.2.jar |
| 26.2 | moltenveins-0.8.1-mc26.2.jar |
moltenveins-neoforge-0.8.1-mc26.2.jar |
| 26.3 | moltenveins-0.8.1-mc26.3.jar |
moltenveins-neoforge-0.8.1-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. 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:ZnDZwOuh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XvxD0SDK:ZnDZwOuh"
}

