Tags
Creators
Details
Licensed MIT
Published last week
Updated 2 days ago
All versions
0.6.3
Beta
MezzConfig 0.6.3 for NeoForge 1.21.12 days ago 19K
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Server-side
Client and server
Changes
- Serialize multiversion release validation - mezz
- Ignore invalid release notification baselines - mezz
- Fix release notification commit tracking - mezz
- Improve migration API to allow rejected values - mezz
- Bump version to 0.5.12 - mezz
- Restore Forge support through 1.21.1 - mezz
- Add NeoForge iconFile - mezz
- Speed up multiversion CI - mezz
- Add project badges to README - mezz
- Create ja_jp.json (#1) - Abbage230
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:7tEfOcA7:zcRUPwOA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7tEfOcA7:zcRUPwOA"
}

