Links
Tags
Creators
Details
Licensed ARR
Published 3 months ago
Updated 3 days ago
All versions
1.5.0+26.3-neoforge
Release
1.5.0+26.3-neoforge3 days ago 9
Uploaded by
Compatibility
Minecraft: Java Edition
26.3
Platform
NeoForge
Supported environments
Client and server
Changes
Added
- NeoForge support on MC 26.3. The 26 NeoForge matrix stopped at 26.2. NeoForge has in fact
shipped 26.3 betas (now
26.3.0.6-beta); what actually failed was ModDevGradle. On 2.0.140 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, so javac rejects the recompiled game before any mod source is compiled. MDG 2.0.147 builds the identical cell clean.
Changed
- 26.3 cell moved from MC 26.3-rc-1 to MC 26.3 (stable, 2026-09-15). The rc-exclusive single-build
window (
26.3-rc.1..26.3-rc.2) is replaced by the ordinary closed prerelease-inclusive range>=26.3- <26.4(Fabric) /[26.3,26.4)(NeoForge). Resourcepack_formatis UNCHANGED at 97 -- it settled at pre-1 and held through pre-2, pre-3, rc-1 and release -- so the rc-1 binary's resources were already correct and only the pin was wrong. - fabric-api
0.160.3+26.3->0.161.0+26.3, NeoForge26.3.0.6-beta, ModDevGradle2.0.147.
Notes
- No source or data change required. The item catalog was re-verified against 26.3 rather than
assumed: all four shipped data files (
keywords.json,categories.json,sort_family.json,sort_type.json) already carry the poplar wood set, the 16-colour cushion / concrete-slab / concrete-stair / wool-slab / wool-stair families,red_shrub,shelf_mushroomandstraw_bed, and they still carry BOTH id sets for the eight explorer maps Mojang renamed at 26.3-pre-1 (8/8 old and 8/8 new in every file). Carrying both is deliberate: on any given version the name that does not exist is inert, whereas swapping fixes 26.3 and silently breaks every cell from 26.3-snapshot-7 down. - 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:GfbuXagl:bJrPhkHd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GfbuXagl:bJrPhkHd"
}

