1.2.1
Compatibility
Changes
Critical Bug Fix and Deprecation
- fix: Config file will now be correctly created on fresh instances, even if the parent directory does not exist.
- deprecated:
Config(String configFileName)is now deprecated in favor ofConfig(Path configPath). Support for the String-based API will be removed in v1.3 (targeted for the next breaking game drop).
This is a non-breaking API update. Existing mods using the String-based constructor will continue to work, but updating is recommended for improved stability, clarity, and future compatibility.
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:WpCaRM4Y:Z3BlLrZr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WpCaRM4Y:Z3BlLrZr"
}

