2.0.0
Compatibility
Changes
Azmine 2.0.0 — Forge 1.12.2
This release brings Azmine to Forge 1.12.2.
No major gameplay changes were made in this version. This is the same Azmine experience from the modern Forge build, adapted for the Minecraft 1.12.2 and Forge environment.
Changes
- Added support for Minecraft 1.12.2
- Added support for Forge 14.23.5.2860
- Updated runtime requirement to Java 8
- Ported networking to the Forge 1.12 custom payload / event-channel system
- Updated mod metadata for Forge 1.12 (mcmod.info)
- Adapted config storage to Forge Configuration (.cfg) while keeping the same options and defaults
- Kept existing mining patterns, HUD, preview, config options, keybinds, and legacy config migration behavior
Compatibility
- Minecraft 1.12.2
- Forge 14.23.5.2860
- Java 8
- Install on both client and server for multiplayer support.
Use Azmine 2.0.0 for the Forge 1.20.1 build, or Azmine 2.1.0 for NeoForge 1.21.1.
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:DO03xtcE:s4Oa91Nq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DO03xtcE:s4Oa91Nq"
}

