Links
Tags
Creators
Details
Licensed ARR
Published 3 months ago
Updated 2 days ago
All versions
1.3.0+26.3
Release
1.3.0+26.32 days ago 9
Compatibility
Minecraft: Java Edition
26.3
Platform
Fabric
Supported environments
Server-side
Singleplayer
Changes
Added
- NeoForge support on MC 26.3. The 26 NeoForge matrix stopped at 26.2 under a "no NeoForge
upstream yet" note that is no longer true -- and was never the real obstacle. NeoForge ships 26.3
betas (now
26.3.0.6-beta); what failed was ModDevGradle. On 2.0.141 the NFRT:createMinecraftArtifactsrecompile dies inside Minecraft's own source (NeoForge's access transformer widensHolderSet.Named.contents()to public and the widening is not propagated to the anonymous subclassHolderSet.emptyNamedreturns), before a line of mod source is compiled. MDG 2.0.147 builds the identical cell clean.
Changed
- 26.3 cell moved from MC 26.3-snapshot-7 to MC 26.3 (stable, 2026-09-15). The snapshot-exclusive
single-build pin is replaced by the ordinary closed prerelease-inclusive range
>=26.3- <26.4(Fabric) /[26.3,26.4)(NeoForge). Resourcepack_format95->97, read from 26.3's ownresources/version.json-- the ladder ran 89..95 across the snapshots then jumped TWO to 97 at pre-1, so it is read and never extrapolated. - fabric-api
0.156.2+26.3->0.161.0+26.3, fabric-loader0.19.3->0.19.5, NeoForge26.3.0.6-beta, ModDevGradle2.0.147.
Notes
- No source change required. The 26.3 gates that land after snapshot-7 were checked against this
mod and none are touched: the pre-1 worldgen /
ChunkStatusmerge,RegionFileStorage,getStructureManager->getStructureTemplateManager, the renamed explorer-map ids, the pre-2tickChunkschange, and the rc-1blockUsingItem/blockedByItemandLevelExtractorchanges. TK4J is server-only and its onlyCommandSourceStackuse is as a type parameter, never a construction, so the pre-1 constructor argument drop does not reach it. - Only the 26.3 cells were rebuilt; every other cell keeps the version it already shipped.
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:IX0J3vJn:QeNOhXU1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:IX0J3vJn:QeNOhXU1"
}

