Links
Tags
Creators
Details
Licensed ARR
Published 3 months ago
Updated 6 days ago
All versions
1.4.0+26.3
Release
1.4.0+26.36 days ago 31
Compatibility
Minecraft: Java Edition
26.3
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Changes
Added
- NeoForge support on MC 26.3. The 26 NeoForge matrix stopped at 26.2 under a "no NeoForge exists
for 26.3 yet" note. It does exist (now
26.3.0.6-beta), and the real obstacle 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, so javac rejects the recompiled game before a line of mod source is compiled. That failure reads exactly like a broken loader, which is how it got recorded as a gap. MDG 2.0.147 builds the identical cell clean. This closes the last loader gap on the 26.3 line: Fabric and NeoForge both ship.
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. - 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 sleeping APIs this mod rides were re-checked: the 4-argument
startSleepInBed(26.3-snapshot-4) andstartSleepinggoing void -> boolean (26.3-snapshot-6) were already handled for the snapshot-7 jar, and nothing in the pre-1 -> release span touches them. The onlyCommandSourceStackcontact isServerPlayer.createCommandSourceStack(), whose own signature is unchanged, so the pre-1 constructor argument drop does not reach this mod. - The Bukkit plugin cell was NOT rebuilt and keeps 1.3.1: one plugin jar spans many MC versions
through its
api-version, so it does not follow the per-26.X model the mod jars do.
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:M1lrtuN1:LTz1PuSa"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:M1lrtuN1:LTz1PuSa"
}
