2.0.0-neoforge
Compatibility
Changes
This release makes changes to the codebase that allows to build the mod for multiple different modloaders via Architectury - starting with Fabric and NeoForge!
There are no additional dependencies that are needed for the mod to function.
Functionality is largely unchanged. This update only concerns multi-modloader support.
NOTE: This version will fail to load. 2.0.1 fixes this issue. Sorry!
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:rd9rKuJT:TrLSWUnx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rd9rKuJT:TrLSWUnx"
}

