Links
Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 4 months ago
Updated 2 days ago
All versions
3.0.1
Release
Legacy API 3.0.13 days ago 14
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.1] - 2026-08-05
Compatibility
- Removed the SDK's hard bytecode link to
net.minecraft.client.Minecraft;McHelpernow resolves the mapped Minecraft class lazily through reflection only when Minecraft-specific helpers are called. - Removed the compile-time
game/jarmodMinecraft 1.4.7 dependencies from the SDK build. The core artifact no longer needs a Minecraft JAR to compile. - Removed unused external ASM 9.5 runtime dependencies; transformer helpers already use the loader's shaded ASM API, avoiding unnecessary ASM classpath conflicts in
-all.jar. MinecraftAutoNetworkBridgeno longer assumes Minecraft 1.4.7. When explicitly enabled it reads-D[sdk].minecraft.version=<version>and disables itself safely if the version or mappings are unavailable.- Added regression coverage that rejects hard
net.minecraft.*type references in the Minecraft-facing SDK classes.
Mapping workflow
- Removed the
.remappingstaging workflow.tools/MinecraftRemappingis now the single source path for mapping data. - Gradle mapping generation reads
tools/MinecraftRemapping/<version>/mcp2obf.srgdirectly from the pinned submodule. - Fixed
SimpleRemapso release JARs actually consume the generated mapping subset; 3.0.0 generatedGeneratedSrgMappingsbut never called it. - Replaced
prepareRemapping/import-submodulewith directinspectMinecraftRemapping,inspect-submodule, andsubmodule-pathworkflows. - Updated
gen_srg_mappings.pyto use project-relative paths instead of a machine-specific absolute Windows path.
Build fixes
- Removed duplicate declarations accidentally left in
build.gradle3.0.0 mapping-generation code.
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:gxSDiq35"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bEmV8Hhn:gxSDiq35"
}

