Перейти к содержимому
Mineforgian

Wireless Redstone Lite

Wireless redstone for Minecraft 26.1.x. Pair transmitter and receiver blocks by channel + frequency — no wire, no spaghetti. Up to 128 blocks of range by default, configurable.

Загрузки
587
Подписчики
2
Обновлён
4 июля 2026 г.
Лицензия
MIT

Опубликован 18 мая 2026 г.

Исходный кодСообщить об ошибке

Wireless Redstone

Wireless Redstone

Tired of running redstone wire through your whole base just to flip one lamp? Drop a transmitter next to your switch, a receiver next to your lamp, match the channel — done. No wire. No floor‑tile mazes. No accidentally powering the wrong piston.

Features

  • Transmitter — takes a redstone input from any side, broadcasts on its channel.
  • Receiver — outputs the strongest signal it sees on its channel, like a redstone block.
  • Channel (1–128) and Frequency (0–65535) — pick any pair to keep your networks separate. Over 8 million combinations per dimension.
  • Lock toggle — freezes the channel/frequency so you can't bump them by accident.
  • Private toggle — binds the pair to your player, so two players can use the same channel without crossing wires on a multiplayer server.
  • Item tooltips show the current config without placing the block — handy for sorting them in a chest.
  • Configurable range — defaults to 128 blocks. Server admins can bump it up to 1024 or disable the limit entirely.

How it works

  1. Craft a transmitter and a receiver (recipes below).
  2. Place the transmitter and feed it redstone from any side — lever, button, comparator, whatever.
  3. Place the receiver anywhere in the same dimension within range.
  4. Right‑click either block to open the config screen. Match the channel + frequency.
  5. The receiver mirrors whatever signal strength the transmitter sees. Strength matters — comparator outputs travel intact.

Multiple transmitters on the same channel? The receiver picks the strongest. Multiple receivers? They all output the same. No cross‑dimension signalling (yet).

Recipes

Transmitter — 4 iron + 3 redstone + 1 ender pearl + 1 redstone block

Recipe for Wireless Transmitter

Receiver — 2 iron + 3 redstone + 1 ender pearl + 1 redstone torch

Recipe for Wireless Receiver

The ender pearl gates these behind your first enderman kill — far enough out that you've explored a bit, but accessible long before diamond or Nether tier.

Configuration

Config file lives at config/wirelessredstone.json (created on first launch):

{
  "rangeLocked": true,
  "maxRange": 128
}
Key Default What it does
rangeLocked true When true, receivers ignore transmitters farther than maxRange blocks. Set false for unlimited range within a dimension.
maxRange 128 Block distance. Clamped to [4, 1024].

Edit the file and restart Minecraft (or the dedicated server) for changes to take effect.

Requirements

  • Minecraft 26.1.x
  • Java 25
  • Fabric Loader 0.18.4+ with Fabric API, or NeoForge 26.1+

Roadmap

Future versions may add: a "fixed strength" mode (transmitter always emits a chosen 1–15 instead of mirroring its input), Jade/WAILA tooltips for in‑world inspection, and an owner‑only Private gamerule.

Source

GitHub: kestalkayden/wireless-redstone — CC0‑1.0.

Ченджлог

0.1.2+mc26.1.2Релиз26.1, 26.1.1, 26.1.2 · 4 июля 2026 г.

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.
0.1.2+mc26.1.2Релиз26.1, 26.1.1, 26.1.2 · 4 июля 2026 г.

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.
0.2.3+mc26.2Релиз26.2 · 4 июля 2026 г.

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.
0.2.3+mc26.2Релиз26.2 · 4 июля 2026 г.

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.
0.2.2+mc26.2Релиз26.2 · 16 июня 2026 г.

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.
0.2.2+mc26.2Релиз26.2 · 16 июня 2026 г.

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.
0.2.1Бета26.2-rc-2 · 16 июня 2026 г.

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.
0.2.0Бета26.2-rc-2 · 16 июня 2026 г.

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.

Комментарии

Загружаем…