1.1-m
Compatibility
Changes
THIS VERSION HAS MOD SUPPORT! DO NOT USE IF YOU WILL NOT BE RUNNING PLUGINS WITH MODS!!
Why is this different? Well some mods use blockstates, so this version has been updated to include blockstates when outputting to the console, so DIAMOND_ORE is now DIAMOND_ORE:0. This is also the same in the config, it uses blockstates.
Why did I add this? Well, some mods use blockstates for a different block. For example, EXAMPLE_ORE:0, and EXAMPLE_ORE:1 are different ores, just like diamond is different from iron. So we need this to manage blockstates for these kinds of ores.
Happy gaming!
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:eimnzGV1:S4pQRjyW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eimnzGV1:S4pQRjyW"
}

