0.2.0+1.20.1FORGE
Compatibility
Changes
No longer a proof of concept
The mod now is fully functional using a world-by-world config. Your world must first be opened once with the mod installed on the relevant server for the config file to generate in serverconfig. On subsequent world restarts, config changes will be applied. The config file contains several comments detailing on how to format your config entries.
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:gDmLsQ5X:GtUZAzY1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gDmLsQ5X:GtUZAzY1"
}

