1.6.0
Compatibility
Changes
First of all, Happy New Year everyone(assuming this release works 😅). This is the first release using a new build system I've been working on that maintains 1.20.4-1.16.5 Fabric/Forge/NeoForge all in the same codebase. Assuming everything goes well, this means that 1.16.5, 1.17.1, 1.18.2, 1.19.2, 1.19.3, 1.19.4, 1.20.2 etc will all become supported and maintained, and contain all the latest and greatest features and bugfixes. Note: 1.8 and 1.12.2 remain unsupported, as the tooling around them is just bad, and their codebases are too different to keep in here.
Changes
- Add 1.20.4 support(1.20.3 is skipped as there's no point to it)
- Add NeoForge support for 1.20.4 and 1.20.2
- Backporting all 1.20.2+ changes/fixes to <= 1.19.4(1.16.5 Forge got a config screen for example 🙃, also 1.16.5 in general now will render player-heads in 3d)
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:zV5r3pPn:jSNusqNF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zV5r3pPn:jSNusqNF"
}

