Links
Tags
Creators
Details
Licensed MIT
Published 2 months ago
Updated 3 weeks ago
All versions
1.2.10+1.21.11-forge
Release
1.2.10+1.21.11-forge3 weeks ago 31
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Forge
Supported environments
Client-side
Changes
Fixed
- Full D1-D22 doctrine re-audit found + fixed real live-boot and resource-pack bugs across
9 cells. Rebuilt and republished the affected (loader, MC) pairs:
- D3 claim-gate over-claims (4 cells), root-caused via built-jar manifest inspection:
Forge/1.21.1claimed MC[1.21,1.21.2)needing javafml 52+, but MC 1.21.0 shipped Forge 51.0.33/javafml 51 -- narrowed to[1.21.1,1.21.2).Forge/1.21.8claimed[1.21.6,1.21.9)needing javafml 58+, but 1.21.6/1.21.7 are permanent orphan Forge builds -- narrowed to[1.21.8,1.21.9).Forge/1.20.6claimed[1.20.5,1.21)but Forge never shipped MC 1.20.5 -- narrowed to[1.20.6,1.21).NeoForge/1.21.1had the same shape ([1.21,1.21.2)vs the neo 21.1 floor, MC 1.21.0 ships neo 21.0.x) -- narrowed to[1.21.1,1.21.2). Each of these previously refused to boot on part of its claimed range. - D3a NeoForge 26.1 over-blocking floor: relaxed
[26.1.2.0-beta,)->[26.1.0-alpha,)-- the mod's actual NeoForge glue uses no 26.1.2-specific API, so the tighter floor was silently blocking 26.1 and 26.1.1 users for no reason. - D4 pack.mcmeta dead-zone (5 cells) -- the mod had never gotten the 2026-07-12 doctrine
correction every sibling mod already carries.
Fabric/1.21.11,NeoForge/1.21.10,NeoForge/1.21.11were shipping the WRONG resource-major pack.mcmeta (should ship NONE -- both loaders synthesise correct metadata in the 1.21.9-1.21.11 dead zone);Forge/1.21.10/1.21.11were shipping the wrong major too (corrected to the DATA-major form, 88/94). A present-but-wrong pack.mcmeta drops the mod's WHOLE resource pack on Forge/NeoForge -- HUD gauge textures and lang were gone for every live user on those versions. Verified in every rebuilt jar (unzip-checked) and client-render smoketested.
- D3 claim-gate over-claims (4 cells), root-caused via built-jar manifest inspection:
Changed
- Version 1.2.9 -> 1.2.10 on the 10 affected cells only (Forge 1.20.6/1.21.1/1.21.8/
1.21.10/1.21.11, NeoForge 1.21.1/1.21.10/1.21.11/26.1, Fabric 1.21.11); every other cell is
byte-unchanged and stays at its prior published version. All 10 rebuilt
-Xlint:allzero warnings; client-render smoketested on Raider (all 10 CELL PASS, HUD instruments verified by eye in every screenshot).
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:plksOJtT:mW1RSpjn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:plksOJtT:mW1RSpjn"
}

