ВЕРСИИ (38)

### Added - **NeoForge support on MC 26.3.** The 26 NeoForge matrix stopped at 26.2 under a "no NeoForge upstream yet" note that is no longer true -- and was never the real obstacle. NeoForge ships 26.3 betas (now `26.3.0.6-beta`); what failed was ModDevGradle. On 2.0.141 the NFRT `:createMinecraftArtifacts` recompile dies 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), before a line of mod source is compiled. MDG 2.0.147 builds the identical cell clean. ### Changed - **26.3 cell moved from MC 26.3-snapshot-7 to MC 26.3 (stable, 2026-09-15).** The snapshot-exclusive single-build pin is replaced by the ordinary closed prerelease-inclusive range `>=26.3- <26.4` (Fabric) / `[26.3,26.4)` (NeoForge). Resource `pack_format` `95` -> `97`, read from 26.3's own `resources/version.json` -- the ladder ran 89..95 across the snapshots then jumped TWO to 97 at pre-1, so it is read and never extrapolated. - fabric-api `0.156.2+26.3` -> `0.161.0+26.3`, fabric-loader `0.19.3` -> `0.19.5`, NeoForge `26.3.0.6-beta`, ModDevGradle `2.0.147`. ### Notes - **No source change required.** The 26.3 gates that land after snapshot-7 were checked against this mod and none are touched: the pre-1 worldgen / `ChunkStatus` merge, `RegionFileStorage`, `getStructureManager` -> `getStructureTemplateManager`, the renamed explorer-map ids, the pre-2 `tickChunks` change, and the rc-1 `blockUsingItem` / `blockedByItem` and `LevelExtractor` changes. TK4J is server-only and its only `CommandSourceStack` use is as a type parameter, never a construction, so the pre-1 constructor argument drop does not reach it. - 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 NeoForge matrix stopped at 26.2 under a "no NeoForge upstream yet" note that is no longer true -- and was never the real obstacle. NeoForge ships 26.3 betas (now `26.3.0.6-beta`); what failed was ModDevGradle. On 2.0.141 the NFRT `:createMinecraftArtifacts` recompile dies 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), before a line of mod source is compiled. MDG 2.0.147 builds the identical cell clean. ### Changed - **26.3 cell moved from MC 26.3-snapshot-7 to MC 26.3 (stable, 2026-09-15).** The snapshot-exclusive single-build pin is replaced by the ordinary closed prerelease-inclusive range `>=26.3- <26.4` (Fabric) / `[26.3,26.4)` (NeoForge). Resource `pack_format` `95` -> `97`, read from 26.3's own `resources/version.json` -- the ladder ran 89..95 across the snapshots then jumped TWO to 97 at pre-1, so it is read and never extrapolated. - fabric-api `0.156.2+26.3` -> `0.161.0+26.3`, fabric-loader `0.19.3` -> `0.19.5`, NeoForge `26.3.0.6-beta`, ModDevGradle `2.0.147`. ### Notes - **No source change required.** The 26.3 gates that land after snapshot-7 were checked against this mod and none are touched: the pre-1 worldgen / `ChunkStatus` merge, `RegionFileStorage`, `getStructureManager` -> `getStructureTemplateManager`, the renamed explorer-map ids, the pre-2 `tickChunks` change, and the rc-1 `blockUsingItem` / `blockedByItem` and `LevelExtractor` changes. TK4J is server-only and its only `CommandSourceStack` use is as a type parameter, never a construction, so the pre-1 constructor argument drop does not reach it. - 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.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

### Changed - **Every jar is now 1.2.13**, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix. ### Fixed - **Claim ranges now match the loader gates.** Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series. - **pack.mcmeta on MC 1.21.9-1.21.11.** The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack. - **AbstractArrow constructor era boundary** in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2. - **Forge and NeoForge jars reported their version as `0.0NONE`.** Those manifests ask the loader to read the version from the jar (`${file.jarVersion}`), but the jar never carried an `Implementation-Version` attribute, so the mod list and every log line showed `0.0NONE`. All 24 loader jars now carry the real version. ### Added - **Ten new build targets**: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.