Links
Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 4 months ago
Updated 2 days ago
All versions
3.0.0
Release
Legacy API 3.0.04 days ago 5
Compatibility
Minecraft: Java Edition
1.12.x
1.11.x
1.10.x
1.9.x
1.8.x
1.7.x
1.6.4
1.6.1–1.6.2
1.5.x
1.4.4–1.4.7
1.4.2
1.3.x
1.2.x
Platform
NilLoader
Supported environments
Client and server
Changes
[3.0.0] - 2026-08-05
Added
- Added
agaricusb/MinecraftRemappingas an external Git submodule configuration attools/MinecraftRemapping, pinned by the bootstrap scripts to8ca7ba25dfd67eae43b3c73d02603ff6c085a6d7. - Added a Java 8-compatible SRG/CSRG mapping API:
SrgMappingSetandSrgMappings. - Added
MappingToolMainwithinspect,reverse,chain,lookup,list-submodule, andimport-submodulecommands, plus a standalonemapping-toolJAR that contains no mapping data. - Added Gradle
mappingToolandprepareRemappingtasks for local mapping workflows. - Added
MAPPINGS.mddocumenting mapping-source policy and local-only import behavior. - Added cross-platform Gradle launcher JVM discovery for Linux/macOS and Windows. JDK 21 and 17 are preferred automatically so a system-wide Java 25 does not break Gradle 8.8.
- Added GitHub Actions
build.ymlfor push/pull-request builds and tests on Ubuntu/Windows with JDK 17/21. - Added GitHub Actions
release.ymlforv*tags. Releases are created only after build/tests succeed, include JARs plus SHA-256 checksums, and use the matchingCHANGE.mdsection as the release body. - Added release helper scripts that verify tag/project version consistency and extract one changelog section.
Changed
- Bumped the SDK and metadata version to
3.0.0. - Java compilation now targets Java 8 with
--release 8while Gradle itself runs on a supported modern launcher JDK; a dedicated local JDK 8 installation is no longer required for normal builds. - Complete mapping collections are no longer shipped in the project ZIP/release tree.
.remapping/remains gitignored and is treated as developer-supplied local build input. - GitHub release responsibilities were separated from normal commit CI:
build.ymlonly validates commits/PRs, whilerelease.ymlowns tagged releases.
Fixed
- Fixed Gradle 8.8 startup failing under Java 25 with
Unsupported class file major version 69by selecting a compatible installed launcher JDK before Gradle starts. - Fixed old mapping workflows relying on copied 100+ MB mapping trees by replacing them with explicit local import tooling and an external submodule reference.
- Mapping parsing now reports conflicting entries instead of silently replacing them, mapping composition keeps method descriptors namespace-correct, and CSRG member resolution no longer depends on class-entry order.
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:bEmV8Hhn:fS6PCFWS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bEmV8Hhn:fS6PCFWS"
}

