15.0.mod
Compatibility
Changes
Bug Fix Update! NOTE: if you downloaded this on May 25th, PLEASE REDOWNLOAD!! Some more critical bugs have been fixed!!
Okay, not much has changed with this, but ideally all issues with Crafting should be resolved, as the data pack now uses its own namespace instead of residing in Minecraft's namespace. That may not mean much to most of you, but basically it means that compatibility with other mods and data packs should be much less of an issue now!
Additionally, there's been a couple small Advancement tweaks; you now no longer receive both the Diamond and Emerald Armor advancements if you craft Emerald Armor first, and the Monster Hunter advancement icon has been reverted to its Vanilla icon instead of the bone I had changed it to. That's it!
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:9eokjKUM:dmnbvT79"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9eokjKUM:dmnbvT79"
}

