4.3.0+forge
Compatibility
Changes
refactor(1.12.2-forge): rename package (domain)
refactor(1.12.2-forge): modular
refacotr(1.12.2-forge): remove support to 1.11.2-1.12.1
style(1.12.2-forge): streamlined config screen
fix(1.12.2-forge): fix an issue of not being able to save config file with screen (#38)
refactor(1.12.2-forge): use TOML instead FNML
feat(1.12.2-forge): auto reset scrolling when cursor moves away from item (#72)
feat(1.12.2-forge): Compatible with LegendaryTooltips (#53)
feat(1.12.2-forge): Compatible with AppleSkin (#82)
feat(1.12.2-forge): Verification required compatible with Apotheosis (#81)
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:mzNYT2LK:mj3qziGq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mzNYT2LK:mj3qziGq"
}

