ВЕРСИИ (153)

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Fixed - **Artificial horizon: the whole ball now rolls with the aircraft.** Only the white aircraft symbol (-o-) used to rotate, while the blue/brown ball and the pitch ladder stayed fixed, so the horizon did not follow the world horizon when banking. The ball and pitch ladder are now rotated by the roll angle and the aircraft symbol is drawn fixed on top of them, like a real attitude indicator. Thank you to DarthJahus, who reported this and contributed the fix (mod_support #47). Only visible with Do a Barrel Roll, which supplies the roll.

### Added - **NeoForge support on MC 26.3.** The 26 line previously stopped at NeoForge 26.2 because 26.3 was believed to have no loader. It does -- `26.3.0.6-beta` -- and the thing that actually blocked it was ModDevGradle: on 2.0.140 the NFRT `:createMinecraftArtifacts` recompile fails inside Minecraft's own source (NeoForge's access transformer widens `HolderSet.Named.contents()` to public and the widening is not propagated to the anonymous subclass `HolderSet.emptyNamed` returns), so javac rejects the recompiled game before a single line of mod source is touched. MDG 2.0.147 builds the identical cell clean. Nothing in this mod's code was involved. ### 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 gone: the jar now carries the ordinary closed prerelease-inclusive range `>=26.3- <26.4` (Fabric) / `[26.3,26.4)` (NeoForge), the same shape every settled 26.X line uses. Resource `pack_format` `95` -> `97`, read from 26.3's own `resources/version.json` -- the 26.3 ladder ran 89,90,91,92,93,94,95 across the snapshots and then jumped TWO to 97 at pre-1, which is exactly why it is read and never incremented. - fabric-api `0.156.2+26.3` -> `0.161.0+26.3`, fabric-loader `0.19.3` -> `0.19.5`, ModMenu `21.0.0-alpha.1` -> `21.0.0-beta.1`, NeoForge `26.3.0.6-beta`, ModDevGradle `2.0.147`. ### Notes - **No source change required.** ElytraHud3 is a client-only HUD mod with no mixins, and the 26.3 breaking surfaces were checked against it one by one: the only renderer symbol it names is `RenderPipelines.GUI_TEXTURED`, handed straight to `GuiGraphics.blit` -- `RenderPipelines` itself did NOT move in the snapshot-3 `com.mojang.blaze3d.*` -> `com.mojang.renderpearl.*` relocation, and the mod never names the moved types, so the blit sites compile unchanged. It touches none of the snapshot-4 SDL input renumbering, the snapshot-6 `InputWithModifiers.getDigit()` removal or options screen reshuffle, the snapshot-7 `swing` / `drop` / `Prediction` breaks, the pre-1 worldgen and `ChunkStatus` merge, or the rc-1 `LevelExtractor` rewrite. - Only the 26.3 cells were rebuilt; every other cell keeps the version it already shipped.

### Added - **NeoForge support on MC 26.3.** The 26 line previously stopped at NeoForge 26.2 because 26.3 was believed to have no loader. It does -- `26.3.0.6-beta` -- and the thing that actually blocked it was ModDevGradle: on 2.0.140 the NFRT `:createMinecraftArtifacts` recompile fails inside Minecraft's own source (NeoForge's access transformer widens `HolderSet.Named.contents()` to public and the widening is not propagated to the anonymous subclass `HolderSet.emptyNamed` returns), so javac rejects the recompiled game before a single line of mod source is touched. MDG 2.0.147 builds the identical cell clean. Nothing in this mod's code was involved. ### 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 gone: the jar now carries the ordinary closed prerelease-inclusive range `>=26.3- <26.4` (Fabric) / `[26.3,26.4)` (NeoForge), the same shape every settled 26.X line uses. Resource `pack_format` `95` -> `97`, read from 26.3's own `resources/version.json` -- the 26.3 ladder ran 89,90,91,92,93,94,95 across the snapshots and then jumped TWO to 97 at pre-1, which is exactly why it is read and never incremented. - fabric-api `0.156.2+26.3` -> `0.161.0+26.3`, fabric-loader `0.19.3` -> `0.19.5`, ModMenu `21.0.0-alpha.1` -> `21.0.0-beta.1`, NeoForge `26.3.0.6-beta`, ModDevGradle `2.0.147`. ### Notes - **No source change required.** ElytraHud3 is a client-only HUD mod with no mixins, and the 26.3 breaking surfaces were checked against it one by one: the only renderer symbol it names is `RenderPipelines.GUI_TEXTURED`, handed straight to `GuiGraphics.blit` -- `RenderPipelines` itself did NOT move in the snapshot-3 `com.mojang.blaze3d.*` -> `com.mojang.renderpearl.*` relocation, and the mod never names the moved types, so the blit sites compile unchanged. It touches none of the snapshot-4 SDL input renumbering, the snapshot-6 `InputWithModifiers.getDigit()` removal or options screen reshuffle, the snapshot-7 `swing` / `drop` / `Prediction` breaks, the pre-1 worldgen and `ChunkStatus` merge, or the rc-1 `LevelExtractor` rewrite. - Only the 26.3 cells were rebuilt; every other cell keeps the version it already shipped.

### Changed - **Fabric 26.3 cell moved to MC 26.3-snapshot-7** (from snapshot-6): fabric-api `0.156.1+26.3` -> `0.156.2+26.3`, resource `pack_format` `94` -> `95`, exclusive window `[26.3-alpha.6, 26.3-alpha.7)` -> `[26.3-alpha.7, 26.3-alpha.8)`. Every 26.3 snapshot bumps pack_format by one, so each jar stays snapshot-exclusive. No other cell changed. ### Notes - **No source change required.** snapshot-7's breaking surfaces were checked against this mod and none are touched: the trailing `Prediction` argument on `LivingEntity.drop(ItemStack, boolean)` / `Inventory.placeItemBackInInventory`, the client-side `LocalPlayer.drop(boolean)` return type going `boolean` -> `void`, the `InteractionResult.SwingSource` `CLIENT`/`SERVER` -> `PREDICTED`/`SERVER_ONLY` rename together with the deletion of `ServerboundSwingPacket`, and the 32 new concrete slab/stair blocks plus the filled-map colour component removals.

### 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.1` claimed 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.8` claimed `[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.6` claimed `[1.20.5,1.21)` but Forge never shipped MC 1.20.5 -- narrowed to `[1.20.6,1.21)`. `NeoForge/1.21.1` had 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.11` were 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.11` were 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. ### 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:all` zero warnings; client-render smoketested on Raider (all 10 CELL PASS, HUD instruments verified by eye in every screenshot).

### 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.1` claimed 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.8` claimed `[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.6` claimed `[1.20.5,1.21)` but Forge never shipped MC 1.20.5 -- narrowed to `[1.20.6,1.21)`. `NeoForge/1.21.1` had 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.11` were 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.11` were 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. ### 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:all` zero warnings; client-render smoketested on Raider (all 10 CELL PASS, HUD instruments verified by eye in every screenshot).

### 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.1` claimed 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.8` claimed `[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.6` claimed `[1.20.5,1.21)` but Forge never shipped MC 1.20.5 -- narrowed to `[1.20.6,1.21)`. `NeoForge/1.21.1` had 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.11` were 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.11` were 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. ### 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:all` zero warnings; client-render smoketested on Raider (all 10 CELL PASS, HUD instruments verified by eye in every screenshot).

### 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.1` claimed 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.8` claimed `[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.6` claimed `[1.20.5,1.21)` but Forge never shipped MC 1.20.5 -- narrowed to `[1.20.6,1.21)`. `NeoForge/1.21.1` had 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.11` were 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.11` were 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. ### 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:all` zero warnings; client-render smoketested on Raider (all 10 CELL PASS, HUD instruments verified by eye in every screenshot).

### 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.1` claimed 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.8` claimed `[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.6` claimed `[1.20.5,1.21)` but Forge never shipped MC 1.20.5 -- narrowed to `[1.20.6,1.21)`. `NeoForge/1.21.1` had 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.11` were 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.11` were 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. ### 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:all` zero warnings; client-render smoketested on Raider (all 10 CELL PASS, HUD instruments verified by eye in every screenshot).

### 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.1` claimed 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.8` claimed `[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.6` claimed `[1.20.5,1.21)` but Forge never shipped MC 1.20.5 -- narrowed to `[1.20.6,1.21)`. `NeoForge/1.21.1` had 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.11` were 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.11` were 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. ### 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:all` zero warnings; client-render smoketested on Raider (all 10 CELL PASS, HUD instruments verified by eye in every screenshot).

### 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.1` claimed 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.8` claimed `[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.6` claimed `[1.20.5,1.21)` but Forge never shipped MC 1.20.5 -- narrowed to `[1.20.6,1.21)`. `NeoForge/1.21.1` had 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.11` were 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.11` were 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. ### 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:all` zero warnings; client-render smoketested on Raider (all 10 CELL PASS, HUD instruments verified by eye in every screenshot).

### 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.1` claimed 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.8` claimed `[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.6` claimed `[1.20.5,1.21)` but Forge never shipped MC 1.20.5 -- narrowed to `[1.20.6,1.21)`. `NeoForge/1.21.1` had 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.11` were 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.11` were 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. ### 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:all` zero warnings; client-render smoketested on Raider (all 10 CELL PASS, HUD instruments verified by eye in every screenshot).

### 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.1` claimed 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.8` claimed `[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.6` claimed `[1.20.5,1.21)` but Forge never shipped MC 1.20.5 -- narrowed to `[1.20.6,1.21)`. `NeoForge/1.21.1` had 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.11` were 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.11` were 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. ### 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:all` zero warnings; client-render smoketested on Raider (all 10 CELL PASS, HUD instruments verified by eye in every screenshot).

### 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.1` claimed 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.8` claimed `[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.6` claimed `[1.20.5,1.21)` but Forge never shipped MC 1.20.5 -- narrowed to `[1.20.6,1.21)`. `NeoForge/1.21.1` had 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.11` were 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.11` were 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. ### 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:all` zero warnings; client-render smoketested on Raider (all 10 CELL PASS, HUD instruments verified by eye in every screenshot).

### Fixed - **The ModMenu pin was wrong on two of the three 26.x rows.** The Fabric 26 cell carried a SINGLE `mod_menu_version=18.0.0` used for 26.1, 26.2 and 26.3 alike -- but ModMenu ships a separate major per MC line (18.x = 26.1, 20.x = 26.2, 21.x = 26.3), and an older major is INTERMEDIARY-named against a newer mojmap MC. So 26.2 and 26.3 were compiling against 26.1-era ModMenu and only got away with it because EH3 touches just the ModMenuApi surface. `mod_menu_version` is now a PER-26.X matrix value in `scripts/build-fabric.ps1` (**26.1 -> 18.0.0, 26.2 -> 20.0.1, 26.3 -> 21.0.0-alpha.1**), passed through as `-P`. Same root cause as the ASR 26.1 build failure. ### Changed - Version 1.2.8 -> **1.2.9**; Fabric 26.1 / 26.2 / 26.3 rebuilt against the correct ModMenu.

### Fixed - **The ModMenu pin was wrong on two of the three 26.x rows.** The Fabric 26 cell carried a SINGLE `mod_menu_version=18.0.0` used for 26.1, 26.2 and 26.3 alike -- but ModMenu ships a separate major per MC line (18.x = 26.1, 20.x = 26.2, 21.x = 26.3), and an older major is INTERMEDIARY-named against a newer mojmap MC. So 26.2 and 26.3 were compiling against 26.1-era ModMenu and only got away with it because EH3 touches just the ModMenuApi surface. `mod_menu_version` is now a PER-26.X matrix value in `scripts/build-fabric.ps1` (**26.1 -> 18.0.0, 26.2 -> 20.0.1, 26.3 -> 21.0.0-alpha.1**), passed through as `-P`. Same root cause as the ASR 26.1 build failure. ### Changed - Version 1.2.8 -> **1.2.9**; Fabric 26.1 / 26.2 / 26.3 rebuilt against the correct ModMenu.

### Fixed - **The ModMenu pin was wrong on two of the three 26.x rows.** The Fabric 26 cell carried a SINGLE `mod_menu_version=18.0.0` used for 26.1, 26.2 and 26.3 alike -- but ModMenu ships a separate major per MC line (18.x = 26.1, 20.x = 26.2, 21.x = 26.3), and an older major is INTERMEDIARY-named against a newer mojmap MC. So 26.2 and 26.3 were compiling against 26.1-era ModMenu and only got away with it because EH3 touches just the ModMenuApi surface. `mod_menu_version` is now a PER-26.X matrix value in `scripts/build-fabric.ps1` (**26.1 -> 18.0.0, 26.2 -> 20.0.1, 26.3 -> 21.0.0-alpha.1**), passed through as `-P`. Same root cause as the ASR 26.1 build failure. ### Changed - Version 1.2.8 -> **1.2.9**; Fabric 26.1 / 26.2 / 26.3 rebuilt against the correct ModMenu.

### Changed - NeoForge 26 cells rebuilt against the now-PUBLISHED NeoForge builds: 26.1 -> 26.1.2.87, 26.2 -> 26.2.0.35-beta (previously 26.1.2.30-beta / 26.2.0.1-beta). The [26.1.2.0-beta,) floor is unchanged. - mavenLocal() removed from the NeoForge/26 cell; the cell README example build command no longer pins the superseded loader build. - No source or behaviour change. Server-boot smoketested on NeoForge 26.1.2 and 26.2.

### Changed - 26.3 Fabric cell retargeted `26.3-snapshot-3` -> `26.3-snapshot-5` (fabric-api 0.155.3+26.3, dep `26.3-alpha.5`, resource pack_format 93). HUD + config screen render clean in-world on the snapshot (headless client-harness eyeballed: all flight instruments draw). - Sourced ModMenu from Modrinth's maven (`maven.modrinth:modmenu`) on the 26 cell instead of `maven.terraformersmc.com`, which stopped serving the 18.x ModMenu artifacts the config-screen entrypoint compiles against. Fabric-only (no NeoForge/Forge upstream on 26.3). Config screen + HUD compile clean against the snap-4 GLFW->SDL / renderpearl API changes. - Build refactor (no behaviour change): eliminated the `_codegen/cog_sources/master/` and `_codegen/cog_sources/common/` source trees, folding them into the `_codegen/cog_sources` single source of truth (D16). ### Added - `publish.json` for the shared `tools/mod-publish/publish.py` publisher; retired the per-version `_publish_eh3_*.py` one-offs.

### Added - MC `26.3-snapshot-3` support (Fabric), snapshot-3 exclusive. Published to Modrinth.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.3 -- Forge coverage extended to 1.21.11 + issue-tracker fix. - NEW: Forge builds for MC 1.21.10 (Forge 60) and 1.21.11 (Forge 61); the overlay-registration API is present on those builds, so Forge now covers through 1.21.11 alongside Fabric and NeoForge. - FIXED: the in-manifest Issues link now points to the central support tracker (github.com/Kishku7/mod_support/issues) on every jar and loader (previously a disabled tab). - No gameplay or rendering changes from 1.2.2. Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API there), Forge 1.21.2 (never shipped), no Forge on 26.x, NeoForge 1.21.9 (beta-only) and no NeoForge 26.3 yet -- use Fabric for those.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

ElytraHud3 1.2.2 -- one source, every version. - The whole 1.20 -> 26.x range now builds from a single unified source tree; every claimed (MC, loader) pair is client-gated (HUD rendered + screenshot-verified in-world). - NEW: Forge support on MC 1.20.2 / 1.20.3 / 1.20.4 (previously only Fabric/NeoForge covered those). - Correct per-version resource pack metadata (fixes missing HUD textures on 1.21.9+ clients). Known gaps (loader limitations, not the mod): Forge 1.21 / 1.21.3 / 1.21.4 / 1.21.6 / 1.21.7 (Forge removed its HUD-overlay registration API on those specific builds), no Forge on 26.x, and NeoForge has not shipped a 26.3 build yet -- use Fabric for those. Fabric + NeoForge cover the rest.

Code Base Refactor

Code Base Refactor

Code Base Refactor

Code Base Refactor

Stable Minecraft 26.2 release. Recompiled against MC 26.2 (release); Fabric API 0.152.1+26.2 / NeoForge 26.2.0.1-beta.

Stable Minecraft 26.2 release. Recompiled against MC 26.2 (release); Fabric API 0.152.1+26.2 / NeoForge 26.2.0.1-beta.

ElytraHud3 1.0.2 - resource metadata fix. Adds the pack.mcmeta descriptor that was missing from the jars so Forge/NeoForge register the HUD's bundled textures (no more 'Missing metadata in pack'). No gameplay changes. Client-side HUD; Fabric/Quilt want Fabric API.

ElytraHud3 1.0.2 - resource metadata fix. Adds the pack.mcmeta descriptor that was missing from the jars so Forge/NeoForge register the HUD's bundled textures (no more 'Missing metadata in pack'). No gameplay changes. Client-side HUD; Fabric/Quilt want Fabric API.

ElytraHud3 1.0.2 - resource metadata fix. Adds the pack.mcmeta descriptor that was missing from the jars so Forge/NeoForge register the HUD's bundled textures (no more 'Missing metadata in pack'). No gameplay changes. Client-side HUD; Fabric/Quilt want Fabric API.

ElytraHud3 1.0.2 - resource metadata fix. Adds the pack.mcmeta descriptor that was missing from the jars so Forge/NeoForge register the HUD's bundled textures (no more 'Missing metadata in pack'). No gameplay changes. Client-side HUD; Fabric/Quilt want Fabric API.

ElytraHud3 1.1.3 - resource metadata fix. Adds the pack.mcmeta resource-pack descriptor that was missing from the jars. On Forge and NeoForge the loader logged a 'Missing metadata in pack' warning and could fail to register the HUD's bundled gauge textures; with pack.mcmeta present the resources load correctly. No gameplay or feature changes - identical HUD, packaged correctly. Pick the version matching your Minecraft version and loader. Client-side HUD - install on the client only. Fabric/Quilt builds want Fabric API.

ElytraHud3 1.1.3 - resource metadata fix. Adds the pack.mcmeta resource-pack descriptor that was missing from the jars. On Forge and NeoForge the loader logged a 'Missing metadata in pack' warning and could fail to register the HUD's bundled gauge textures; with pack.mcmeta present the resources load correctly. No gameplay or feature changes - identical HUD, packaged correctly. Pick the version matching your Minecraft version and loader. Client-side HUD - install on the client only. Fabric/Quilt builds want Fabric API.

ElytraHud3 1.1.3 - resource metadata fix. Adds the pack.mcmeta resource-pack descriptor that was missing from the jars. On Forge and NeoForge the loader logged a 'Missing metadata in pack' warning and could fail to register the HUD's bundled gauge textures; with pack.mcmeta present the resources load correctly. No gameplay or feature changes - identical HUD, packaged correctly. Pick the version matching your Minecraft version and loader. Client-side HUD - install on the client only. Fabric/Quilt builds want Fabric API.

ElytraHud3 1.1.3 - resource metadata fix. Adds the pack.mcmeta resource-pack descriptor that was missing from the jars. On Forge and NeoForge the loader logged a 'Missing metadata in pack' warning and could fail to register the HUD's bundled gauge textures; with pack.mcmeta present the resources load correctly. No gameplay or feature changes - identical HUD, packaged correctly. Pick the version matching your Minecraft version and loader. Client-side HUD - install on the client only. Fabric/Quilt builds want Fabric API.

ElytraHud3 1.1.3 - resource metadata fix. Adds the pack.mcmeta resource-pack descriptor that was missing from the jars. On Forge and NeoForge the loader logged a 'Missing metadata in pack' warning and could fail to register the HUD's bundled gauge textures; with pack.mcmeta present the resources load correctly. No gameplay or feature changes - identical HUD, packaged correctly. Pick the version matching your Minecraft version and loader. Client-side HUD - install on the client only. Fabric/Quilt builds want Fabric API.

ElytraHud3 1.1.3 - resource metadata fix. Adds the pack.mcmeta resource-pack descriptor that was missing from the jars. On Forge and NeoForge the loader logged a 'Missing metadata in pack' warning and could fail to register the HUD's bundled gauge textures; with pack.mcmeta present the resources load correctly. No gameplay or feature changes - identical HUD, packaged correctly. Pick the version matching your Minecraft version and loader. Client-side HUD - install on the client only. Fabric/Quilt builds want Fabric API.

ElytraHud3 1.1.3 - resource metadata fix. Adds the pack.mcmeta resource-pack descriptor that was missing from the jars. On Forge and NeoForge the loader logged a 'Missing metadata in pack' warning and could fail to register the HUD's bundled gauge textures; with pack.mcmeta present the resources load correctly. No gameplay or feature changes - identical HUD, packaged correctly. Pick the version matching your Minecraft version and loader. Client-side HUD - install on the client only. Fabric/Quilt builds want Fabric API.

ElytraHud3 1.1.3 - resource metadata fix. Adds the pack.mcmeta resource-pack descriptor that was missing from the jars. On Forge and NeoForge the loader logged a 'Missing metadata in pack' warning and could fail to register the HUD's bundled gauge textures; with pack.mcmeta present the resources load correctly. No gameplay or feature changes - identical HUD, packaged correctly. Pick the version matching your Minecraft version and loader. Client-side HUD - install on the client only. Fabric/Quilt builds want Fabric API.

ElytraHud3 1.1.3 - resource metadata fix. Adds the pack.mcmeta resource-pack descriptor that was missing from the jars. On Forge and NeoForge the loader logged a 'Missing metadata in pack' warning and could fail to register the HUD's bundled gauge textures; with pack.mcmeta present the resources load correctly. No gameplay or feature changes - identical HUD, packaged correctly. Pick the version matching your Minecraft version and loader. Client-side HUD - install on the client only. Fabric/Quilt builds want Fabric API.

ElytraHud3 1.1.3 - resource metadata fix. Adds the pack.mcmeta resource-pack descriptor that was missing from the jars. On Forge and NeoForge the loader logged a 'Missing metadata in pack' warning and could fail to register the HUD's bundled gauge textures; with pack.mcmeta present the resources load correctly. No gameplay or feature changes - identical HUD, packaged correctly. Pick the version matching your Minecraft version and loader. Client-side HUD - install on the client only. Fabric/Quilt builds want Fabric API.

ElytraHud3 1.1.3 - resource metadata fix. Adds the pack.mcmeta resource-pack descriptor that was missing from the jars. On Forge and NeoForge the loader logged a 'Missing metadata in pack' warning and could fail to register the HUD's bundled gauge textures; with pack.mcmeta present the resources load correctly. No gameplay or feature changes - identical HUD, packaged correctly. Pick the version matching your Minecraft version and loader. Client-side HUD - install on the client only. Fabric/Quilt builds want Fabric API.

ElytraHud3 1.1.3 - resource metadata fix. Adds the pack.mcmeta resource-pack descriptor that was missing from the jars. On Forge and NeoForge the loader logged a 'Missing metadata in pack' warning and could fail to register the HUD's bundled gauge textures; with pack.mcmeta present the resources load correctly. No gameplay or feature changes - identical HUD, packaged correctly. Pick the version matching your Minecraft version and loader. Client-side HUD - install on the client only. Fabric/Quilt builds want Fabric API.

ElytraHud3 1.1.3 - resource metadata fix. Adds the pack.mcmeta resource-pack descriptor that was missing from the jars. On Forge and NeoForge the loader logged a 'Missing metadata in pack' warning and could fail to register the HUD's bundled gauge textures; with pack.mcmeta present the resources load correctly. No gameplay or feature changes - identical HUD, packaged correctly. Pick the version matching your Minecraft version and loader. Client-side HUD - install on the client only. Fabric/Quilt builds want Fabric API.

ElytraHud3 1.1.3 - resource metadata fix. Adds the pack.mcmeta resource-pack descriptor that was missing from the jars. On Forge and NeoForge the loader logged a 'Missing metadata in pack' warning and could fail to register the HUD's bundled gauge textures; with pack.mcmeta present the resources load correctly. No gameplay or feature changes - identical HUD, packaged correctly. Pick the version matching your Minecraft version and loader. Client-side HUD - install on the client only. Fabric/Quilt builds want Fabric API.

ElytraHud3 1.1.3 - resource metadata fix. Adds the pack.mcmeta resource-pack descriptor that was missing from the jars. On Forge and NeoForge the loader logged a 'Missing metadata in pack' warning and could fail to register the HUD's bundled gauge textures; with pack.mcmeta present the resources load correctly. No gameplay or feature changes - identical HUD, packaged correctly. Pick the version matching your Minecraft version and loader. Client-side HUD - install on the client only. Fabric/Quilt builds want Fabric API.

ElytraHud3 1.1.3 - resource metadata fix. Adds the pack.mcmeta resource-pack descriptor that was missing from the jars. On Forge and NeoForge the loader logged a 'Missing metadata in pack' warning and could fail to register the HUD's bundled gauge textures; with pack.mcmeta present the resources load correctly. No gameplay or feature changes - identical HUD, packaged correctly. Pick the version matching your Minecraft version and loader. Client-side HUD - install on the client only. Fabric/Quilt builds want Fabric API.

ElytraHud3 1.1.3 - resource metadata fix. Adds the pack.mcmeta resource-pack descriptor that was missing from the jars. On Forge and NeoForge the loader logged a 'Missing metadata in pack' warning and could fail to register the HUD's bundled gauge textures; with pack.mcmeta present the resources load correctly. No gameplay or feature changes - identical HUD, packaged correctly. Pick the version matching your Minecraft version and loader. Client-side HUD - install on the client only. Fabric/Quilt builds want Fabric API.

ElytraHud3 1.1.0 - massive version backfill (Minecraft 1.20 through 1.21.11). ElytraHud3 now supports the entire 1.20.x and 1.21.x lines in addition to 26.x. Builds are unmerged: one jar per loader per Minecraft build, so any issue maps to exactly one artifact. Pick the version matching your Minecraft version and loader. Coverage: Fabric (and Quilt) plus NeoForge across 1.20.1-1.21.11; Forge through 1.21.8. The Forge 1.20.1 jar also loads on NeoForge 1.20.1. ElytraHud3 is a client-side HUD - install it on the client only. Fabric/Quilt builds want Fabric API; ModMenu and Do a Barrel Roll are optional.

ElytraHud3 1.1.0 - massive version backfill (Minecraft 1.20 through 1.21.11). ElytraHud3 now supports the entire 1.20.x and 1.21.x lines in addition to 26.x. Builds are unmerged: one jar per loader per Minecraft build, so any issue maps to exactly one artifact. Pick the version matching your Minecraft version and loader. Coverage: Fabric (and Quilt) plus NeoForge across 1.20.1-1.21.11; Forge through 1.21.8. The Forge 1.20.1 jar also loads on NeoForge 1.20.1. ElytraHud3 is a client-side HUD - install it on the client only. Fabric/Quilt builds want Fabric API; ModMenu and Do a Barrel Roll are optional.

ElytraHud3 1.1.0 - massive version backfill (Minecraft 1.20 through 1.21.11). ElytraHud3 now supports the entire 1.20.x and 1.21.x lines in addition to 26.x. Builds are unmerged: one jar per loader per Minecraft build, so any issue maps to exactly one artifact. Pick the version matching your Minecraft version and loader. Coverage: Fabric (and Quilt) plus NeoForge across 1.20.1-1.21.11; Forge through 1.21.8. The Forge 1.20.1 jar also loads on NeoForge 1.20.1. ElytraHud3 is a client-side HUD - install it on the client only. Fabric/Quilt builds want Fabric API; ModMenu and Do a Barrel Roll are optional.

ElytraHud3 1.1.0 - massive version backfill (Minecraft 1.20 through 1.21.11). ElytraHud3 now supports the entire 1.20.x and 1.21.x lines in addition to 26.x. Builds are unmerged: one jar per loader per Minecraft build, so any issue maps to exactly one artifact. Pick the version matching your Minecraft version and loader. Coverage: Fabric (and Quilt) plus NeoForge across 1.20.1-1.21.11; Forge through 1.21.8. The Forge 1.20.1 jar also loads on NeoForge 1.20.1. ElytraHud3 is a client-side HUD - install it on the client only. Fabric/Quilt builds want Fabric API; ModMenu and Do a Barrel Roll are optional.

ElytraHud3 1.1.0 - massive version backfill (Minecraft 1.20 through 1.21.11). ElytraHud3 now supports the entire 1.20.x and 1.21.x lines in addition to 26.x. Builds are unmerged: one jar per loader per Minecraft build, so any issue maps to exactly one artifact. Pick the version matching your Minecraft version and loader. Coverage: Fabric (and Quilt) plus NeoForge across 1.20.1-1.21.11; Forge through 1.21.8. The Forge 1.20.1 jar also loads on NeoForge 1.20.1. ElytraHud3 is a client-side HUD - install it on the client only. Fabric/Quilt builds want Fabric API; ModMenu and Do a Barrel Roll are optional.

ElytraHud3 1.1.0 - massive version backfill (Minecraft 1.20 through 1.21.11). ElytraHud3 now supports the entire 1.20.x and 1.21.x lines in addition to 26.x. Builds are unmerged: one jar per loader per Minecraft build, so any issue maps to exactly one artifact. Pick the version matching your Minecraft version and loader. Coverage: Fabric (and Quilt) plus NeoForge across 1.20.1-1.21.11; Forge through 1.21.8. The Forge 1.20.1 jar also loads on NeoForge 1.20.1. ElytraHud3 is a client-side HUD - install it on the client only. Fabric/Quilt builds want Fabric API; ModMenu and Do a Barrel Roll are optional.

ElytraHud3 1.1.0 - massive version backfill (Minecraft 1.20 through 1.21.11). ElytraHud3 now supports the entire 1.20.x and 1.21.x lines in addition to 26.x. Builds are unmerged: one jar per loader per Minecraft build, so any issue maps to exactly one artifact. Pick the version matching your Minecraft version and loader. Coverage: Fabric (and Quilt) plus NeoForge across 1.20.1-1.21.11; Forge through 1.21.8. The Forge 1.20.1 jar also loads on NeoForge 1.20.1. ElytraHud3 is a client-side HUD - install it on the client only. Fabric/Quilt builds want Fabric API; ModMenu and Do a Barrel Roll are optional.

ElytraHud3 1.1.0 - massive version backfill (Minecraft 1.20 through 1.21.11). ElytraHud3 now supports the entire 1.20.x and 1.21.x lines in addition to 26.x. Builds are unmerged: one jar per loader per Minecraft build, so any issue maps to exactly one artifact. Pick the version matching your Minecraft version and loader. Coverage: Fabric (and Quilt) plus NeoForge across 1.20.1-1.21.11; Forge through 1.21.8. The Forge 1.20.1 jar also loads on NeoForge 1.20.1. ElytraHud3 is a client-side HUD - install it on the client only. Fabric/Quilt builds want Fabric API; ModMenu and Do a Barrel Roll are optional.

ElytraHud3 1.1.0 - massive version backfill (Minecraft 1.20 through 1.21.11). ElytraHud3 now supports the entire 1.20.x and 1.21.x lines in addition to 26.x. Builds are unmerged: one jar per loader per Minecraft build, so any issue maps to exactly one artifact. Pick the version matching your Minecraft version and loader. Coverage: Fabric (and Quilt) plus NeoForge across 1.20.1-1.21.11; Forge through 1.21.8. The Forge 1.20.1 jar also loads on NeoForge 1.20.1. ElytraHud3 is a client-side HUD - install it on the client only. Fabric/Quilt builds want Fabric API; ModMenu and Do a Barrel Roll are optional.

ElytraHud3 1.1.0 - massive version backfill (Minecraft 1.20 through 1.21.11). ElytraHud3 now supports the entire 1.20.x and 1.21.x lines in addition to 26.x. Builds are unmerged: one jar per loader per Minecraft build, so any issue maps to exactly one artifact. Pick the version matching your Minecraft version and loader. Coverage: Fabric (and Quilt) plus NeoForge across 1.20.1-1.21.11; Forge through 1.21.8. The Forge 1.20.1 jar also loads on NeoForge 1.20.1. ElytraHud3 is a client-side HUD - install it on the client only. Fabric/Quilt builds want Fabric API; ModMenu and Do a Barrel Roll are optional.

ElytraHud3 1.1.0 - massive version backfill (Minecraft 1.20 through 1.21.11). ElytraHud3 now supports the entire 1.20.x and 1.21.x lines in addition to 26.x. Builds are unmerged: one jar per loader per Minecraft build, so any issue maps to exactly one artifact. Pick the version matching your Minecraft version and loader. Coverage: Fabric (and Quilt) plus NeoForge across 1.20.1-1.21.11; Forge through 1.21.8. The Forge 1.20.1 jar also loads on NeoForge 1.20.1. ElytraHud3 is a client-side HUD - install it on the client only. Fabric/Quilt builds want Fabric API; ModMenu and Do a Barrel Roll are optional.

ElytraHud3 1.1.0 - massive version backfill (Minecraft 1.20 through 1.21.11). ElytraHud3 now supports the entire 1.20.x and 1.21.x lines in addition to 26.x. Builds are unmerged: one jar per loader per Minecraft build, so any issue maps to exactly one artifact. Pick the version matching your Minecraft version and loader. Coverage: Fabric (and Quilt) plus NeoForge across 1.20.1-1.21.11; Forge through 1.21.8. The Forge 1.20.1 jar also loads on NeoForge 1.20.1. ElytraHud3 is a client-side HUD - install it on the client only. Fabric/Quilt builds want Fabric API; ModMenu and Do a Barrel Roll are optional.

ElytraHud3 1.1.0 - massive version backfill (Minecraft 1.20 through 1.21.11). ElytraHud3 now supports the entire 1.20.x and 1.21.x lines in addition to 26.x. Builds are unmerged: one jar per loader per Minecraft build, so any issue maps to exactly one artifact. Pick the version matching your Minecraft version and loader. Coverage: Fabric (and Quilt) plus NeoForge across 1.20.1-1.21.11; Forge through 1.21.8. The Forge 1.20.1 jar also loads on NeoForge 1.20.1. ElytraHud3 is a client-side HUD - install it on the client only. Fabric/Quilt builds want Fabric API; ModMenu and Do a Barrel Roll are optional.

ElytraHud3 1.1.0 - massive version backfill (Minecraft 1.20 through 1.21.11). ElytraHud3 now supports the entire 1.20.x and 1.21.x lines in addition to 26.x. Builds are unmerged: one jar per loader per Minecraft build, so any issue maps to exactly one artifact. Pick the version matching your Minecraft version and loader. Coverage: Fabric (and Quilt) plus NeoForge across 1.20.1-1.21.11; Forge through 1.21.8. The Forge 1.20.1 jar also loads on NeoForge 1.20.1. ElytraHud3 is a client-side HUD - install it on the client only. Fabric/Quilt builds want Fabric API; ModMenu and Do a Barrel Roll are optional.

ElytraHud3 1.1.0 - massive version backfill (Minecraft 1.20 through 1.21.11). ElytraHud3 now supports the entire 1.20.x and 1.21.x lines in addition to 26.x. Builds are unmerged: one jar per loader per Minecraft build, so any issue maps to exactly one artifact. Pick the version matching your Minecraft version and loader. Coverage: Fabric (and Quilt) plus NeoForge across 1.20.1-1.21.11; Forge through 1.21.8. The Forge 1.20.1 jar also loads on NeoForge 1.20.1. ElytraHud3 is a client-side HUD - install it on the client only. Fabric/Quilt builds want Fabric API; ModMenu and Do a Barrel Roll are optional.

ElytraHud3 1.1.0 - massive version backfill (Minecraft 1.20 through 1.21.11). ElytraHud3 now supports the entire 1.20.x and 1.21.x lines in addition to 26.x. Builds are unmerged: one jar per loader per Minecraft build, so any issue maps to exactly one artifact. Pick the version matching your Minecraft version and loader. Coverage: Fabric (and Quilt) plus NeoForge across 1.20.1-1.21.11; Forge through 1.21.8. The Forge 1.20.1 jar also loads on NeoForge 1.20.1. ElytraHud3 is a client-side HUD - install it on the client only. Fabric/Quilt builds want Fabric API; ModMenu and Do a Barrel Roll are optional.

ElytraHud3 1.1.0 - massive version backfill (Minecraft 1.20 through 1.21.11). ElytraHud3 now supports the entire 1.20.x and 1.21.x lines in addition to 26.x. Builds are unmerged: one jar per loader per Minecraft build, so any issue maps to exactly one artifact. Pick the version matching your Minecraft version and loader. Coverage: Fabric (and Quilt) plus NeoForge across 1.20.1-1.21.11; Forge through 1.21.8. The Forge 1.20.1 jar also loads on NeoForge 1.20.1. ElytraHud3 is a client-side HUD - install it on the client only. Fabric/Quilt builds want Fabric API; ModMenu and Do a Barrel Roll are optional.

26.2-rc-2 support.

26.2-rc-2 support.