### Fixed - **Boats could not be crafted on MC 1.21 and 1.21.1** (mod_support #43). The recipes shipped in `data/lavaboats/recipes/`, but 1.21 renamed that folder to `recipe/` and loads nothing from the old name -- no error, the boats were simply in the creative menu and nowhere in a crafting table. The resource generator moved the folder at 1.21.2 together with the recipe schema change; the folder actually moved one release earlier. Rebuilt cells: Fabric 1.21.1 (covers 1.21-1.21.1), Forge 1.21, Forge 1.21.1, NeoForge 1.21, NeoForge 1.21.1. Every other cell keeps the version it shipped.

### Fixed - **Boats could not be crafted on MC 1.21 and 1.21.1** (mod_support #43). The recipes shipped in `data/lavaboats/recipes/`, but 1.21 renamed that folder to `recipe/` and loads nothing from the old name -- no error, the boats were simply in the creative menu and nowhere in a crafting table. The resource generator moved the folder at 1.21.2 together with the recipe schema change; the folder actually moved one release earlier. Rebuilt cells: Fabric 1.21.1 (covers 1.21-1.21.1), Forge 1.21, Forge 1.21.1, NeoForge 1.21, NeoForge 1.21.1. Every other cell keeps the version it shipped.

### Fixed - **Boats could not be crafted on MC 1.21 and 1.21.1** (mod_support #43). The recipes shipped in `data/lavaboats/recipes/`, but 1.21 renamed that folder to `recipe/` and loads nothing from the old name -- no error, the boats were simply in the creative menu and nowhere in a crafting table. The resource generator moved the folder at 1.21.2 together with the recipe schema change; the folder actually moved one release earlier. Rebuilt cells: Fabric 1.21.1 (covers 1.21-1.21.1), Forge 1.21, Forge 1.21.1, NeoForge 1.21, NeoForge 1.21.1. Every other cell keeps the version it shipped.

### Fixed - **Boats could not be crafted on MC 1.21 and 1.21.1** (mod_support #43). The recipes shipped in `data/lavaboats/recipes/`, but 1.21 renamed that folder to `recipe/` and loads nothing from the old name -- no error, the boats were simply in the creative menu and nowhere in a crafting table. The resource generator moved the folder at 1.21.2 together with the recipe schema change; the folder actually moved one release earlier. Rebuilt cells: Fabric 1.21.1 (covers 1.21-1.21.1), Forge 1.21, Forge 1.21.1, NeoForge 1.21, NeoForge 1.21.1. Every other cell keeps the version it shipped.

### Fixed - **Boats could not be crafted on MC 1.21 and 1.21.1** (mod_support #43). The recipes shipped in `data/lavaboats/recipes/`, but 1.21 renamed that folder to `recipe/` and loads nothing from the old name -- no error, the boats were simply in the creative menu and nowhere in a crafting table. The resource generator moved the folder at 1.21.2 together with the recipe schema change; the folder actually moved one release earlier. Rebuilt cells: Fabric 1.21.1 (covers 1.21-1.21.1), Forge 1.21, Forge 1.21.1, NeoForge 1.21, NeoForge 1.21.1. Every other cell keeps the version it shipped.

### Added - **NeoForge support on MC 26.3.** The 26 NeoForge matrix stopped at 26.2 under a "no 26.3 loader" note that was wrong twice over: NeoForge has shipped 26.3 betas (now `26.3.0.6-beta`), and the thing that actually 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, so javac rejects the recompiled game before any mod source is compiled. That reads exactly like a broken loader, which is how it got recorded as one. 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 26.3 ladder ran 89,90,91,92,93,94,95 across the snapshots and 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 one by one and none are touched: the pre-1 worldgen rewrite and `ChunkStatus` NOISE/SURFACE/ CARVERS merge, `RegionFileStorage`, `getStructureManager` -> `getStructureTemplateManager`, the eight renamed explorer-map item ids, the pre-2 `tickChunks` change, the rc-1 `blockUsingItem` / `blockedByItem` re-signature and `LevelExtractor` rewrite. The mod's mixins target boat buoyancy and fluid status, which the 26.3 line does not move. - 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 26.3 loader" note that was wrong twice over: NeoForge has shipped 26.3 betas (now `26.3.0.6-beta`), and the thing that actually 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, so javac rejects the recompiled game before any mod source is compiled. That reads exactly like a broken loader, which is how it got recorded as one. 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 26.3 ladder ran 89,90,91,92,93,94,95 across the snapshots and 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 one by one and none are touched: the pre-1 worldgen rewrite and `ChunkStatus` NOISE/SURFACE/ CARVERS merge, `RegionFileStorage`, `getStructureManager` -> `getStructureTemplateManager`, the eight renamed explorer-map item ids, the pre-2 `tickChunks` change, the rc-1 `blockUsingItem` / `blockedByItem` re-signature and `LevelExtractor` rewrite. The mod's mixins target boat buoyancy and fluid status, which the 26.3 line does not move. - Only the 26.3 cells were rebuilt; every other cell keeps the version it already shipped.

### Fixed - **Lava boats sank on dedicated servers.** The two mixins that create lava buoyancy -- `AbstractBoatLavaMixin` (the float boost and resurface bob) and the per-loader fluid hook (`BoatWaterFabricMixin` / `BoatFluidForgeMixin` / `BoatFluidNeoForgeMixin`) -- were registered under the `"client"` key of their mixin configs, so Mixin skipped them entirely in a SERVER environment. On a dedicated server `AbstractBoat.getStatus()` never saw lava as water, the status resolved to `IN_AIR`, and `floatBoat()` applied full gravity with no float boost. Because `tick()` gates `floatBoat()` on `isLocalInstanceAuthoritative()` -- true on the server whenever nobody is riding -- an unridden boat fell to the bottom of the lava, and a ridden one sank as soon as authority returned to the server (dismount, relog, chunk reload). Both mixins now register under `"mixins"` and run in either environment. - Single-player was never affected, which is why this went unnoticed: an integrated server runs inside the client JVM, where the client-only configs apply normally. - **Every jar from 1.4.0 through 1.4.9 was affected**, on all three loaders and every MC version from 1.20.1 to 26.3. The mixins were common before the 1.4.0 single-source unification; that commit filed them under `"client"` and silently undid the earlier multiplayer-sink fix. ### Changed - Both fluid hooks now declare `require = 3` on their three-method `@Redirect`. Mixin's default of `require = 1` accepts a single successful injection out of the three target methods, so a partial application could pass silently; all three are now mandatory. - Full 44-jar matrix rebuilt (Fabric 10 / Forge 15 / NeoForge 19), `-Xlint:all` clean, zero javac warnings. - **D23 -- the loader now reports the real mod version.** Forge and early-NeoForge cells declare `version = "${file.jarVersion}"` in mods.toml, which FML fills from the jar manifest's `Implementation-Version`; that attribute was never written, so 18 cells reported `0.0NONE` to the loader and Forge/NeoForge 1.20.6 reported a stale hardcoded `1.2.0`. Every Forge and NeoForge cell now stamps `Implementation-Title` / `Implementation-Version` / `Implementation-Vendor`, with the `-forge` / `-neoforge` filename suffix stripped from the value. Caught by the pre-publish metadata gate, which lava-boats had never been run through before. ### Testing - New **float gate** (`Server_Tests/lavaboat-float-gate/` on the harness) -- a server-side BEHAVIOUR gate in the shape of the storm and catch-up gates. It builds a stone basin, fills it with three layers of lava, summons an UNRIDDEN boat above it, and asserts the boat's Y at 6s and 12s. A boot smoketest cannot see this bug: the mod loads clean and logs nothing. - **Proven in both directions before being trusted.** Pre-fix jars report Y=101.0 (resting on the basin floor, three lava layers down) on both the 1.20 `Boat` line and the 1.21.2+ `AbstractBoat` line; fixed jars report Y=103.72, stable across both samples. - CRITICAL tier green on all three loaders: Fabric 1.20.1 / 1.21.1 / 1.21.11 / 26.1.2 / 26.2 / 26.3-snapshot-7, NeoForge 1.20.1 / 1.21.1 / 1.21.11 / 26.1.2, Forge 1.20.1 / 1.21.1 / 1.21.11.

### Fixed - **Lava boats sank on dedicated servers.** The two mixins that create lava buoyancy -- `AbstractBoatLavaMixin` (the float boost and resurface bob) and the per-loader fluid hook (`BoatWaterFabricMixin` / `BoatFluidForgeMixin` / `BoatFluidNeoForgeMixin`) -- were registered under the `"client"` key of their mixin configs, so Mixin skipped them entirely in a SERVER environment. On a dedicated server `AbstractBoat.getStatus()` never saw lava as water, the status resolved to `IN_AIR`, and `floatBoat()` applied full gravity with no float boost. Because `tick()` gates `floatBoat()` on `isLocalInstanceAuthoritative()` -- true on the server whenever nobody is riding -- an unridden boat fell to the bottom of the lava, and a ridden one sank as soon as authority returned to the server (dismount, relog, chunk reload). Both mixins now register under `"mixins"` and run in either environment. - Single-player was never affected, which is why this went unnoticed: an integrated server runs inside the client JVM, where the client-only configs apply normally. - **Every jar from 1.4.0 through 1.4.9 was affected**, on all three loaders and every MC version from 1.20.1 to 26.3. The mixins were common before the 1.4.0 single-source unification; that commit filed them under `"client"` and silently undid the earlier multiplayer-sink fix. ### Changed - Both fluid hooks now declare `require = 3` on their three-method `@Redirect`. Mixin's default of `require = 1` accepts a single successful injection out of the three target methods, so a partial application could pass silently; all three are now mandatory. - Full 44-jar matrix rebuilt (Fabric 10 / Forge 15 / NeoForge 19), `-Xlint:all` clean, zero javac warnings. - **D23 -- the loader now reports the real mod version.** Forge and early-NeoForge cells declare `version = "${file.jarVersion}"` in mods.toml, which FML fills from the jar manifest's `Implementation-Version`; that attribute was never written, so 18 cells reported `0.0NONE` to the loader and Forge/NeoForge 1.20.6 reported a stale hardcoded `1.2.0`. Every Forge and NeoForge cell now stamps `Implementation-Title` / `Implementation-Version` / `Implementation-Vendor`, with the `-forge` / `-neoforge` filename suffix stripped from the value. Caught by the pre-publish metadata gate, which lava-boats had never been run through before. ### Testing - New **float gate** (`Server_Tests/lavaboat-float-gate/` on the harness) -- a server-side BEHAVIOUR gate in the shape of the storm and catch-up gates. It builds a stone basin, fills it with three layers of lava, summons an UNRIDDEN boat above it, and asserts the boat's Y at 6s and 12s. A boot smoketest cannot see this bug: the mod loads clean and logs nothing. - **Proven in both directions before being trusted.** Pre-fix jars report Y=101.0 (resting on the basin floor, three lava layers down) on both the 1.20 `Boat` line and the 1.21.2+ `AbstractBoat` line; fixed jars report Y=103.72, stable across both samples. - CRITICAL tier green on all three loaders: Fabric 1.20.1 / 1.21.1 / 1.21.11 / 26.1.2 / 26.2 / 26.3-snapshot-7, NeoForge 1.20.1 / 1.21.1 / 1.21.11 / 26.1.2, Forge 1.20.1 / 1.21.1 / 1.21.11.

### Fixed - **Lava boats sank on dedicated servers.** The two mixins that create lava buoyancy -- `AbstractBoatLavaMixin` (the float boost and resurface bob) and the per-loader fluid hook (`BoatWaterFabricMixin` / `BoatFluidForgeMixin` / `BoatFluidNeoForgeMixin`) -- were registered under the `"client"` key of their mixin configs, so Mixin skipped them entirely in a SERVER environment. On a dedicated server `AbstractBoat.getStatus()` never saw lava as water, the status resolved to `IN_AIR`, and `floatBoat()` applied full gravity with no float boost. Because `tick()` gates `floatBoat()` on `isLocalInstanceAuthoritative()` -- true on the server whenever nobody is riding -- an unridden boat fell to the bottom of the lava, and a ridden one sank as soon as authority returned to the server (dismount, relog, chunk reload). Both mixins now register under `"mixins"` and run in either environment. - Single-player was never affected, which is why this went unnoticed: an integrated server runs inside the client JVM, where the client-only configs apply normally. - **Every jar from 1.4.0 through 1.4.9 was affected**, on all three loaders and every MC version from 1.20.1 to 26.3. The mixins were common before the 1.4.0 single-source unification; that commit filed them under `"client"` and silently undid the earlier multiplayer-sink fix. ### Changed - Both fluid hooks now declare `require = 3` on their three-method `@Redirect`. Mixin's default of `require = 1` accepts a single successful injection out of the three target methods, so a partial application could pass silently; all three are now mandatory. - Full 44-jar matrix rebuilt (Fabric 10 / Forge 15 / NeoForge 19), `-Xlint:all` clean, zero javac warnings. - **D23 -- the loader now reports the real mod version.** Forge and early-NeoForge cells declare `version = "${file.jarVersion}"` in mods.toml, which FML fills from the jar manifest's `Implementation-Version`; that attribute was never written, so 18 cells reported `0.0NONE` to the loader and Forge/NeoForge 1.20.6 reported a stale hardcoded `1.2.0`. Every Forge and NeoForge cell now stamps `Implementation-Title` / `Implementation-Version` / `Implementation-Vendor`, with the `-forge` / `-neoforge` filename suffix stripped from the value. Caught by the pre-publish metadata gate, which lava-boats had never been run through before. ### Testing - New **float gate** (`Server_Tests/lavaboat-float-gate/` on the harness) -- a server-side BEHAVIOUR gate in the shape of the storm and catch-up gates. It builds a stone basin, fills it with three layers of lava, summons an UNRIDDEN boat above it, and asserts the boat's Y at 6s and 12s. A boot smoketest cannot see this bug: the mod loads clean and logs nothing. - **Proven in both directions before being trusted.** Pre-fix jars report Y=101.0 (resting on the basin floor, three lava layers down) on both the 1.20 `Boat` line and the 1.21.2+ `AbstractBoat` line; fixed jars report Y=103.72, stable across both samples. - CRITICAL tier green on all three loaders: Fabric 1.20.1 / 1.21.1 / 1.21.11 / 26.1.2 / 26.2 / 26.3-snapshot-7, NeoForge 1.20.1 / 1.21.1 / 1.21.11 / 26.1.2, Forge 1.20.1 / 1.21.1 / 1.21.11.