Tags
Creators
Details
1.3.9
Compatibility
Changes
Fixed a startup NullPointerException on Velocity/Sponge: if the bundled default config.toml resource could not be loaded (e.g. missing/unreadable in the classpath) or the config file failed to load for any reason, the config object was left null and every settings getter crashed on first use. loadConfig() now falls back to the bundled default (or an empty config with safe defaults) instead of leaving config null, so the plugin can still start. Development/test build for verification before promotion to a stable release.
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:GWjFNPSB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:y05wfnBZ:GWjFNPSB"
}

