Tags
Creators
Details
0.6.1+26.1.2
Compatibility
Changes
0.6.1
Added
- Added translated config value tooltips with
ValueBuilder.tooltipKey(String).
Changed
-
Completely reorganized Konfig's core to give configuration storage, migration, screens, synchronization, runtime setup, and loader integration clear boundaries. This makes behavior easier to keep consistent across every supported Minecraft version and loader.
-
Documented the supported
api.v1addon API and marked implementation types as internal so addon authors can clearly distinguish stable APIs from details that may change between releases. -
See the Konfig README for a guide on how to add Konfig support to your mod.
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:yDopFlad"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pp7kIrlM:yDopFlad"
}

