Step 2 of #8. versions/1.21.10/src is gone; 1.21.10 builds from src/ as
:1.21.10, with versions/1.21.10 keeping only gradle.properties and run/.
API differences go behind version comments: render layers (ShaderUtils),
Camera.update's World vs BlockView (CameraMixin), the text and textured-quad
render states (RenderScopeImpl), Screen.init (SplashOverlayMixin) and
jspecify's @NonNull (SaturnRenderState).
Features 1.21.11 leaves out stay on 1.21.10, with a TODO for 1.21.11:
WorldFeatureImpl.getWorldAge, SaturnScreenFabric.resize and
EntityDrawerImpl clearing the hitbox.
Hats now render on 1.21.10: its HatFeatureRenderer overrode the
render-queue method with an empty body, and the working code sat in an old
VertexConsumerProvider method nothing called. 1.21.10 now uses 1.21.11's
render-queue implementation (HatFeatureRenderer, ObjModel, ObjRenderer),
and also gets 1.21.11's null check on the player's display name.
The 1.21.10 jar has the same entries, fabric.mod.json and mixin configs as
before; only those four classes and ShaderUtils (a helper method for
entityAlpha) have different bytecode. The 1.21.11 jar only differs in
ShaderUtils.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
- settings.gradle, stonecutter.gradle and the root build.gradle become
.kts. Loom's version for the Stonecutter versions moves to the root
gradle.properties (loom_version), read by pluginManagement, since the
Kotlin plugins block can't read properties. The old mc-<v> projects keep
their Groovy scripts until they're folded in.
- buildAll ran all eight remapJar tasks at once. Each loads a Minecraft
classpath and remaps a ~50 MB jar, which doesn't fit in the 3 GB daemon
heap: a cold build stalled in garbage collection for 40+ minutes, and
earlier runs failed. A shared build service now lets two remaps run
together; a cold buildAll takes about 2 minutes.
- port.sh and VERSION_GUIDE follow the .kts file names.
The 1.21.11 jar is the same as with the Groovy scripts.
Co-Authored-By: Claude Opus 5.5 <[email protected]>