ВЕРСИИ (26)

## Fixed - **Jade no longer wipes your selected resource packs.** With Jade installed, Wireless Redstone's tooltip plugin was missing two config-screen translations; Jade flagged that on the title screen and the game responded by deselecting every resource pack, on every launch. The translations are now included. ## Notes - No world or config changes. Same fix as v0.3.0 on the Minecraft 26.3 line.

## Fixed - **Jade no longer wipes your selected resource packs.** With Jade installed, Wireless Redstone's tooltip plugin was missing two config-screen translations; Jade flagged that on the title screen and the game responded by deselecting every resource pack, on every launch. The translations are now included. ## Notes - No world or config changes. Same fix as v0.3.0 on the Minecraft 26.3 line.

## Fixed - **Jade no longer wipes your selected resource packs.** With Jade installed, Wireless Redstone's tooltip plugin was missing two config-screen translations; Jade flagged that on the title screen and the game responded by deselecting every resource pack, on every launch. The translations are now included. ## Notes - No world or config changes. Same fix as v0.3.0 on the Minecraft 26.3 line.

## Fixed - **Jade no longer wipes your selected resource packs.** With Jade installed, Wireless Redstone's tooltip plugin was missing two config-screen translations; Jade flagged that on the title screen and the game responded by deselecting every resource pack, on every launch. The translations are now included. ## Notes - No world or config changes. Same fix as v0.3.0 on the Minecraft 26.3 line.

## Changed - Updated for **Minecraft 26.3** (Fabric Loader 0.19.5+ / Fabric API 0.161.0+; NeoForge `26.3.0.7-beta`+). Requires Minecraft 26.3. ## Fixed - **Jade no longer wipes your selected resource packs.** With Jade installed, Wireless Redstone's tooltip plugin was missing two config-screen translations; Jade flagged that on the title screen and the game responded by deselecting every resource pack, on every launch. The translations are now included. - Ported to the 26.3 APIs: block codecs (removed from the game), the renamed piston push-reaction constants, and the 26.3 resource/data pack formats. ## Notes - NeoForge for 26.3 is still in **beta**; this build targets `26.3.0.7-beta`. - No world or config changes; existing transmitters, receivers, and pairings carry over.

## Changed - Updated for **Minecraft 26.3** (Fabric Loader 0.19.5+ / Fabric API 0.161.0+; NeoForge `26.3.0.7-beta`+). Requires Minecraft 26.3. ## Fixed - **Jade no longer wipes your selected resource packs.** With Jade installed, Wireless Redstone's tooltip plugin was missing two config-screen translations; Jade flagged that on the title screen and the game responded by deselecting every resource pack, on every launch. The translations are now included. - Ported to the 26.3 APIs: block codecs (removed from the game), the renamed piston push-reaction constants, and the 26.3 resource/data pack formats. ## Notes - NeoForge for 26.3 is still in **beta**; this build targets `26.3.0.7-beta`. - No world or config changes; existing transmitters, receivers, and pairings carry over.

## Changed - Internal packaging metadata (`pack.mcmeta`) now declares the correct resource and data pack formats for Minecraft 26.1.2. ## Notes - **Nothing changes for players** — this build behaves identically to v0.1.3. No new features, no gameplay changes. - The old values worked in practice, because Minecraft does not enforce pack formats for mod-bundled resources. This corrects them so the mod keeps working if that ever changes.

## Changed - Internal packaging metadata (`pack.mcmeta`) now declares the correct resource and data pack formats for Minecraft 26.1.2. ## Notes - **Nothing changes for players** — this build behaves identically to v0.1.3. No new features, no gameplay changes. - The old values worked in practice, because Minecraft does not enforce pack formats for mod-bundled resources. This corrects them so the mod keeps working if that ever changes.

## Changed - Internal packaging metadata (`pack.mcmeta`) now declares the correct resource and data pack formats for Minecraft 26.2. ## Notes - **Nothing changes for players** — this build behaves identically to v0.2.4. No new features, no gameplay changes. - The old values worked in practice, because Minecraft does not enforce pack formats for mod-bundled resources. This corrects them so the mod keeps working if that ever changes.

## Changed - Internal packaging metadata (`pack.mcmeta`) now declares the correct resource and data pack formats for Minecraft 26.2. ## Notes - **Nothing changes for players** — this build behaves identically to v0.2.4. No new features, no gameplay changes. - The old values worked in practice, because Minecraft does not enforce pack formats for mod-bundled resources. This corrects them so the mod keeps working if that ever changes.

## Fixed - **Transmitters no longer get stuck on next to their own receiver.** A transmitter placed within a block of a receiver on the same channel and frequency could latch on: once its redstone input (lever, comparator, etc.) switched it on, it stayed on even after that input turned off — or was removed entirely. Transmitters now ignore the signal from receivers on their own channel when reading their input, so they release correctly. Receivers driving a transmitter on a *different* channel are unaffected.

## Fixed - **Transmitters no longer get stuck on next to their own receiver.** A transmitter placed within a block of a receiver on the same channel and frequency could latch on: once its redstone input (lever, comparator, etc.) switched it on, it stayed on even after that input turned off — or was removed entirely. Transmitters now ignore the signal from receivers on their own channel when reading their input, so they release correctly. Receivers driving a transmitter on a *different* channel are unaffected.

## Fixed - **Transmitters no longer get stuck on next to their own receiver.** A transmitter placed within a block of a receiver on the same channel and frequency could latch on: once its redstone input (lever, comparator, etc.) switched it on, it stayed on even after that input turned off — or was removed entirely. Transmitters now ignore the signal from receivers on their own channel when reading their input, so they release correctly. Receivers driving a transmitter on a *different* channel are unaffected.

## Fixed - **Transmitters no longer get stuck on next to their own receiver.** A transmitter placed within a block of a receiver on the same channel and frequency could latch on: once its redstone input (lever, comparator, etc.) switched it on, it stayed on even after that input turned off — or was removed entirely. Transmitters now ignore the signal from receivers on their own channel when reading their input, so they release correctly. Receivers driving a transmitter on a *different* channel are unaffected.

## Changed - **Lock and Private now actually protect a block.** Only the player who placed it (or a server operator / creative-mode player) can open its config or change a transmitter's mode. Previously any player could retune or toggle any block. - Large wireless networks are much lighter on the server: a signal change now only nudges the receivers whose output actually changes, instead of every block sharing the frequency. - The "Paired: N receivers" / "Receiving from N" counts on the config screens now only include blocks that are actually within range. ## Fixed - Transmitters and receivers no longer go dead after being broken and re-placed (or moved by a hopper, or pick-blocked in creative) — they keep their channel and frequency. - Receivers now behave like a redstone block: they power adjacent dust and components but no longer push a signal *through* a solid block, and no longer leave a stale "ghost" signal behind an adjacent block. - A config screen left open after its block was broken can no longer create a permanent phantom signal. - Transmitters in Fixed / Always On / Always Off mode no longer re-broadcast to the whole network when their redstone input changes without changing the output. - On NeoForge, receivers no longer fire a redundant redstone neighbor update when their chunk loads. - Hardened server-side handling of edit-lock, value limits, and network packets against malformed or unauthorized input.

## Changed - **Lock and Private now actually protect a block.** Only the player who placed it (or a server operator / creative-mode player) can open its config or change a transmitter's mode. Previously any player could retune or toggle any block. - Large wireless networks are much lighter on the server: a signal change now only nudges the receivers whose output actually changes, instead of every block sharing the frequency. - The "Paired: N receivers" / "Receiving from N" counts on the config screens now only include blocks that are actually within range. ## Fixed - Transmitters and receivers no longer go dead after being broken and re-placed (or moved by a hopper, or pick-blocked in creative) — they keep their channel and frequency. - Receivers now behave like a redstone block: they power adjacent dust and components but no longer push a signal *through* a solid block, and no longer leave a stale "ghost" signal behind an adjacent block. - A config screen left open after its block was broken can no longer create a permanent phantom signal. - Transmitters in Fixed / Always On / Always Off mode no longer re-broadcast to the whole network when their redstone input changes without changing the output. - On NeoForge, receivers no longer fire a redundant redstone neighbor update when their chunk loads. - Hardened server-side handling of edit-lock, value limits, and network packets against malformed or unauthorized input.

## Changed - **Lock and Private now actually protect a block.** Only the player who placed it (or a server operator / creative-mode player) can open its config or change a transmitter's mode. Previously any player could retune or toggle any block. - Large wireless networks are much lighter on the server: a signal change now only nudges the receivers whose output actually changes, instead of every block sharing the frequency. - The "Paired: N receivers" / "Receiving from N" counts on the config screens now only include blocks that are actually within range. ## Fixed - Transmitters and receivers no longer go dead after being broken and re-placed (or moved by a hopper, or pick-blocked in creative) — they keep their channel and frequency. - Receivers now behave like a redstone block: they power adjacent dust and components but no longer push a signal *through* a solid block, and no longer leave a stale "ghost" signal behind an adjacent block. - A config screen left open after its block was broken can no longer create a permanent phantom signal. - Transmitters in Fixed / Always On / Always Off mode no longer re-broadcast to the whole network when their redstone input changes without changing the output. - Hardened server-side handling of edit-lock, value limits, and network packets against malformed or unauthorized input.

## Changed - **Lock and Private now actually protect a block.** Only the player who placed it (or a server operator / creative-mode player) can open its config or change a transmitter's mode. Previously any player could retune or toggle any block. - Large wireless networks are much lighter on the server: a signal change now only nudges the receivers whose output actually changes, instead of every block sharing the frequency. - The "Paired: N receivers" / "Receiving from N" counts on the config screens now only include blocks that are actually within range. ## Fixed - Transmitters and receivers no longer go dead after being broken and re-placed (or moved by a hopper, or pick-blocked in creative) — they keep their channel and frequency. - Receivers now behave like a redstone block: they power adjacent dust and components but no longer push a signal *through* a solid block, and no longer leave a stale "ghost" signal behind an adjacent block. - A config screen left open after its block was broken can no longer create a permanent phantom signal. - Transmitters in Fixed / Always On / Always Off mode no longer re-broadcast to the whole network when their redstone input changes without changing the output. - Hardened server-side handling of edit-lock, value limits, and network packets against malformed or unauthorized input.

## Changed - Updated for Minecraft 26.2 (final). The earlier 0.2.1 build targeted the 26.2 release candidate and will not load on 26.2 final — update to this version. ## Added - NeoForge builds for 26.2 (on NeoForge `26.2.0.0-beta`); the release-candidate builds were Fabric-only while NeoForged had not yet shipped a 26.2 build.

## Changed - Updated for Minecraft 26.2 (final). The earlier 0.2.1 build targeted the 26.2 release candidate and will not load on 26.2 final — update to this version. ## Added - NeoForge builds for 26.2 (on NeoForge `26.2.0.0-beta`); the release-candidate builds were Fabric-only while NeoForged had not yet shipped a 26.2 build.

# v0.2.1 ## Fixed - Now loads on **Minecraft 26.2-rc.2**. The previous build pinned the Fabric dependency to `26.2-rc-2` (the build-artifact name) instead of the in-game version id Fabric checks at runtime (`26.2-rc.2`), so the loader rejected the mod on launch.

# v0.2.0 ## Changed - Updated for **Minecraft 26.2-rc-2** (Fabric). No change to behavior. ## Notes - **Fabric only, for now.** NeoForge has not published a 26.2 build yet — the NeoForge release will follow once it does. - Built and pinned specifically against `26.2-rc-2`. A later release candidate or the final 26.2 release may need a separate build, so treat this as a testing build. - Jade tooltips remain an optional integration; a Jade build for 26.2 is required to see them in-game.