Tags
Creators
Details
0.10.2+26.3
Compatibility
Changes
0.10.2
Changed
- Config screens before 26.1 show the mod's name and short setting names.
Fixed
-
Config files no longer repeat their header comment on every save.
-
Invalid Fieldset catalog values no longer trap focus.
-
Fieldset catalogs show the error for the rule being edited.
-
Long Fieldset catalog messages fit narrow windows.
-
Fieldset screens no longer recheck every rule on each frame.
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:pp7kIrlM:90QKflPG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pp7kIrlM:90QKflPG"
}

