Links
Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 4 months ago
Updated 2 days ago
All versions
3.0.2
Release
Legacy API 3.0.22 days ago 9
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
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.2] - 2026-08-06
Developer toolbox
- Added the optional
[SDK]-3.0.2-all.jardeveloper toolbox with Byte Buddy1.17.6, Byte Buddy Agent1.17.6, GEB core0.5.4, ClassGraph4.8.184, and SnakeYAML2.6, keeping upstream package names unrelocated for direct imports. - Added
DeveloperToolboxcapability checks plusByteBuddyHelper,ClassGraphHelper,YamlHelper, andGebHelperconvenience APIs. - Byte Buddy self-attachment remains explicit; SDK startup never calls
ByteBuddyAgent.install()automatically. - YAML helpers use
SafeConstructor, reject duplicate mapping keys, and cap aliases for safer configuration loading. - Moved GEB's
processorto the GradleannotationProcessorconfiguration. It is build-time tooling and is not bundled in the runtime shadow JAR. - Optional toolbox dependencies are available to SDK compilation/tests but are not published as transitive dependencies of the normal Maven artifact.
Build and publishing
- Ensured
assemble/buildcreates the-all.jarand standalone-mapping-tool.jaralongside the normal JAR. - Attached both classified JARs to the Maven publication so project-local GPG publishing signs them together with sources/Javadocs.
- Moved signing configuration after classified artifact attachment and added project license/implementation metadata to the standalone mapping-tool JAR.
- Simplified the Windows Gradle launcher to respect the active
JAVA_HOMEselected byactions/setup-javabefore scanning other installed JDKs, while still rejecting unsupported Java 25 for Gradle 8.8. - Preserved service-provider metadata in the shadow JAR and added third-party notices/license files to the distribution.
- Restored GitHub Actions
build.ymlfor Ubuntu/Windows on JDK 17/21 andrelease.ymlforv*tags, including tag/version validation, changelog extraction, SHA-256 checksums, and GitHub Release creation. - Restored release helper scripts and a submodule guard that detects a missing
160000Git link fortools/MinecraftRemapping.
Fixed and documented
- Replaced the accidental Gradle snippet previously stored in
THIRD_PARTY_LICENSES.mdwith an actual third-party license inventory. - Updated stale
3.0.1metadata and documentation references to the in-development3.0.2release. - Kept complete mapping data outside release artifacts; mapping input continues to come directly from
tools/MinecraftRemapping.
Supplementary resources
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:1eMZlXaf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bEmV8Hhn:1eMZlXaf"
}

