0.3.1
Compatibility
Changes
Yes there is now a whole new forge system because Stone Forge is finally here, and it basically lets you melt, smash, cook, and bully ores into new materials. And speaking of ores, Tin is now a thing — Tin Ore, Raw Tin, Tin Ingots, and even a full Block of Tin because why not, stacking is fun.
And since I clearly don’t know how to stop adding metals, Bronze is now craftable too, AND Bismuth Bronze exists because I thought “hey what if bronze but shinier and also bismuth.” There’s also Bismuth Nuggets because nuggets are cute and Minecraft loves nuggets.
So yeah, Forge Reforged basically reforges the entire early‑game metal progression. You get new ores, new alloys, new blocks, and a whole Stone Forge machine to actually do stuff with them. My maths says this update adds like… a LOT of smelting potential, but I’m not doing the maths again after the filter incident.
Yeah that’s everything in this update.
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:yam0g9Fj:E7oHiazR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yam0g9Fj:E7oHiazR"
}

