Tags
Creators
Details
1.3.10
Compatibility
Changes
Made the bundled default config.toml lookup on Velocity/Sponge more robust: it now tries multiple classloaders (a single lookup strategy was returning null on some setups, causing config.toml to never get written to disk). If the bundled resource genuinely cannot be found anywhere, a minimal recovery config.toml is now written to disk instead of silently running in-memory only. Development/test build.
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:y05wfnBZ:CD6echsn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:y05wfnBZ:CD6echsn"
}

