Wireless Redstone adds Redstone components to Minecraft, allowing Redstone components to be controlled remotely. The concept works like any transceiver functionality.
Transmitter and receiver blocks behave in a lazy-loaded manner with respect to redstone updates in unloaded chunks. This means that unloaded chunks will not be actively loaded to make the redstone update, but as soon as the receiver is loaded, its redstone state will be updated to match that of its corresponding transmitter.
New:
- P2P Transmitters and Receivers, added with version 1.2.0
Currently wireless redstone is dimensional but this might change in the future.
Content
Redstone Transmitter & Receiver
The Redstone Transmitter transmits a signal to the Redstone Network when it is turned on by a Redstone signal and sets all receivers on the same frequency to high as well. If there is more than one transmitter transmitting on the same frequency, all receivers on that frequency will be high as long as at least one transmitter on that frequency is on. This block can be right-clicked to set the frequency.
The Redstone Receiver will output a Redstone signal of 15 as long as there is at least one active transmitter on the same frequency. This block can be right-clicked to set the frequency.
P2P Transmitter & Receiver
In addition to the classic frequency based transmitter and receiver pair, there are now P2P transmitters and receivers. Instead of "connecting" them via a frequency, they are directly connected with the help of the Linker, thus the name P2P (point to point). This means that there cannot be any frequency clashes with other players. But you can only connect one transmitter to one receiver and vice versa.
These components have two block states:
powered: Indicating whether the block is being powered (transmitter) or powers something (receiver)linked: Indicating if the block is linked with its counterpart. This property can be tested for by using a comparator. It will output redstone power of 15 if linked, and 0 otherwise.
Once the link between a transmitter and receiver pair is established, the linked property changes accordingly and redstone changes on the transmitter are reflected by the connected receiver. In case one of the two blocks gets destroyed or relinked to another block, the link of its counterpart is terminated.
There is however a unique catch to the linked property. Once a linked p2p block gets unloaded it will visually be unlinked from its counterpart. The redstone state stays the same and the actual link between them is still stored and re-established once they are both loaded again. In case the other block gets destroyed or re-linked in the meantime the block will unlink completely as soon as it tries to connect to the other block again (meaning both must be loaded). This behavior can for example be used detect if certain chunks are loaded or unloaded. I'd like to see what you can come
up with using this feature.
Remote
The Remote is the item form of the Transmitter, while holding right-click the remote signal goes high. But it comes with the addition of being able to copy the frequency of a Transmitter or a Receiver by sneaking and right-clicking it. By sneaking and right-clicking the remote (not on a transmitter/receiver), you can set the frequency through the GUI.
Frequency Tool
The Frequency Tool is a handy tool that makes it easy for you to take a frequency and set multiple transmitters and/or receivers to the same frequency. When holding it in your hand you can copy a frequency into the Frequency Tool by sneaking and right-clicking on a transmitter or receivers. To copy the now-stored frequency, simply right-click either a transmitter or receiver. By sneaking and right-clicking the frequency tool (not on a transmitter/receiver), you can set the frequency through the GUI.
Frequency Sniffer
The Frequency Sniffer can be used as a tool to find active transmitters on a given frequency. As with other frequency tools too you can set the frequency either manually over the gui or copying it from a transmitter/receiver. When you right-click the sniffer tool all active transmitters on the set frequency within range are highlighted with a wireframe around the transmitter block. There is also a chat message that tells you where all the active transmitters are located at by showing the block position. If you are an admin/op, you can also click on the block position to teleport there. See example in the screenshot section. You can also change the highlight color in the configs!
Linker
You use the Linker to link a P2P Transmitter and a P2P Receiver together. By sneaking and right-clicking on a block you select this block for linkage. The selected block is highlighted and can be seen through other blocks, the position of it can also be seen in the tooltip of the Linker item. The color of this highlight can be adjusted in the configs. To complete the link, simply right-click the blocks counterpart and you are done.
Circuit
The Circuit is for crafting purposes only.
GUIs
Note: If you press Shift in the Frequency GUI, all values to change the frequency will be multiplied by 100 (so you can add/subtract 100 and 1000) or you can just type in your desired frequency manually. You can also change the color of the frequency display on a receiver/transmitter in the Configs. The same goes for highlighting with the Frequency Sniffer!
Version & Loader Compatibility
In general Wireless Redstone should always be compatible between mod loaders. Meaning you can enter a world you began with Forge and later switch to Fabric and everything should still work with Wireless Redstone. The same is true for Minecraft versions. Newer versions of Minecraft and the mod should always be backwards compatible with older ones. That being said, always make a backup of your world before switching loaders or versions and open an issue if something of Wireless Redstone isn't working anymore.
All Versions
+ Add Version| Name | Game version | Platforms | Published | Downloads | Actions |
|---|---|---|---|---|---|
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 | ||||
| 14h ago | 1 |
### Added
- Attachment** block version of Redstone Transmitter/Receiver and P2P Redstone Transmitter/Receiver
- Configurable Attachment Mode: Define if the attachment block shall receive/output redstone only from/to the attached block or also all adjacent ones (except the opposite of the attached side)
- Target is shown underneath the crosshair when a P2P block is looked at with a **Linker**
- Frequency items show a message after a frequency has been copied or set
### Changed
- Receivers are now updated immediately after a transmitter is (un)powered (before: 1 redstone tick delay)
- This also allows to send 1 game ticks to receivers (e.g. with an observer)
- Use int array tag (NBT) for storing block positions (transmitters, p2p link, ...)
- This change is *only* backwards compatible (i.e., you can upgrade to newer versions but going back to older one will break the redstone network)
- Improved names and descriptions in config screen
- Redstone transmitters and receivers now also update directly after block placement (also with
/setblockand/fillcommand) - If you place a transmitter with a frequency (e.g., picked up in creative with CTRL, it also shows the frequency in the tooltip), it will now correctly register itself in the redstone ether network, before it did not do that
- If you place a receiver with a frequency it will turn on if any transmitters on the frequency are on
- Note: Frequency receivers (transmitters not) now also work when relocated with frames from project-red
### Fixed
- Sniffer stack size is supposed to be 1
- Sniffer and target highlight render wobbling when far out in the world due to floating point number precision (the farther out, the bigger the wobble)
- P2P transmitter and receiver block entities not updating data correctly
- Fabric**:
- Wrong mixin configuration (was only registered on the client, oops)
- Redstone wire not connecting to transmitters and receivers (if played on server)
- Frequency activated with remote stayed on if:
- Switching to another item in hotbar
- Dropped by player (if played on server)
- Normal usage (releasing right mouse button, if played on server)
[1.3.0+1.20.1]: https://github.com/Razzokk/wireless-redstone/compare/v1.2.2+1.20.1...v1.3.0+1.20.1
### Added
- Attachment** block version of Redstone Transmitter/Receiver and P2P Redstone Transmitter/Receiver
- Configurable Attachment Mode: Define if the attachment block shall receive/output redstone only from/to the attached block or also all adjacent ones (except the opposite of the attached side)
- Target is shown underneath the crosshair when a P2P block is looked at with a **Linker**
- Frequency items show a message after a frequency has been copied or set
### Changed
- Receivers are now updated immediately after a transmitter is (un)powered (before: 1 redstone tick delay)
- This also allows to send 1 game ticks to receivers (e.g. with an observer)
- Use int array tag (NBT) for storing block positions (transmitters, p2p link, ...)
- This change is *only* backwards compatible (i.e., you can upgrade to newer versions but going back to older one will break the redstone network)
- Improved names and descriptions in config screen
- Redstone transmitters and receivers now also update directly after block placement (also with
/setblockand/fillcommand) - If you place a transmitter with a frequency (e.g., picked up in creative with CTRL, it also shows the frequency in the tooltip), it will now correctly register itself in the redstone ether network, before it did not do that
- If you place a receiver with a frequency it will turn on if any transmitters on the frequency are on
- Note: Frequency receivers (transmitters not) now also work when relocated with frames from project-red
### Fixed
- Sniffer stack size is supposed to be 1
- Sniffer and target highlight render wobbling when far out in the world due to floating point number precision (the farther out, the bigger the wobble)
- P2P transmitter and receiver block entities not updating data correctly
- Fabric**:
- Wrong mixin configuration (was only registered on the client, oops)
- Redstone wire not connecting to transmitters and receivers (if played on server)
- Frequency activated with remote stayed on if:
- Switching to another item in hotbar
- Dropped by player (if played on server)
- Normal usage (releasing right mouse button, if played on server)
[1.3.0+1.20.1]: https://github.com/Razzokk/wireless-redstone/compare/v1.2.2+1.20.1...v1.3.0+1.20.1
### Added
- Attachment** block version of Redstone Transmitter/Receiver and P2P Redstone Transmitter/Receiver
- Configurable Attachment Mode: Define if the attachment block shall receive/output redstone only from/to the attached block or also all adjacent ones (except the opposite of the attached side)
- Target is shown underneath the crosshair when a P2P block is looked at with a **Linker**
- Frequency items show a message after a frequency has been copied or set
### Changed
- Receivers are now updated immediately after a transmitter is (un)powered (before: 1 redstone tick delay)
- This also allows to send 1 game ticks to receivers (e.g. with an observer)
- Use int array tag (NBT) for storing block positions (transmitters, p2p link, ...)
- This change is *only* backwards compatible (i.e., you can upgrade to newer versions but going back to older one will break the redstone network)
- Improved names and descriptions in config screen
- Redstone transmitters and receivers now also update directly after block placement (also with
/setblockand/fillcommand) - If you place a transmitter with a frequency (e.g., picked up in creative with CTRL, it also shows the frequency in the tooltip), it will now correctly register itself in the redstone ether network, before it did not do that
- If you place a receiver with a frequency it will turn on if any transmitters on the frequency are on
- Note: Frequency receivers (transmitters not) now also work when relocated with frames from project-red
### Fixed
- Sniffer stack size is supposed to be 1
- Sniffer and target highlight render wobbling when far out in the world due to floating point number precision (the farther out, the bigger the wobble)
- P2P transmitter and receiver block entities not updating data correctly
- Fabric:
- Wrong mixin configuration (was only registered on the client, oops)
- Redstone wire not connecting to transmitters and receivers (if played on server)
- Frequency activated with remote stayed on if:
- Switching to another item in hotbar
- Dropped by player (if played on server)
- Normal usage (releasing right mouse button, if played on server)
- Forge (**1.20.4**):
- Minecraft startup crash with forge version of the mod (used invalid unobfuscated jar)
- Affected versions (**1.2.0**, **1.2.1**, **1.2.2**)
[1.3.0+1.20.4]: https://github.com/Razzokk/wireless-redstone/compare/v1.2.2+1.20.4...v1.3.0+1.20.4
### Added
- Attachment** block version of Redstone Transmitter/Receiver and P2P Redstone Transmitter/Receiver
- Configurable Attachment Mode: Define if the attachment block shall receive/output redstone only from/to the attached block or also all adjacent ones (except the opposite of the attached side)
- Target is shown underneath the crosshair when a P2P block is looked at with a **Linker**
- Frequency items show a message after a frequency has been copied or set
### Changed
- Receivers are now updated immediately after a transmitter is (un)powered (before: 1 redstone tick delay)
- This also allows to send 1 game ticks to receivers (e.g. with an observer)
- Use int array tag (NBT) for storing block positions (transmitters, p2p link, ...)
- This change is *only* backwards compatible (i.e., you can upgrade to newer versions but going back to older one will break the redstone network)
- Improved names and descriptions in config screen
- Redstone transmitters and receivers now also update directly after block placement (also with
/setblockand/fillcommand) - If you place a transmitter with a frequency (e.g., picked up in creative with CTRL, it also shows the frequency in the tooltip), it will now correctly register itself in the redstone ether network, before it did not do that
- If you place a receiver with a frequency it will turn on if any transmitters on the frequency are on
- Note: Frequency receivers (transmitters not) now also work when relocated with frames from project-red
### Fixed
- Sniffer stack size is supposed to be 1
- Sniffer and target highlight render wobbling when far out in the world due to floating point number precision (the farther out, the bigger the wobble)
- P2P transmitter and receiver block entities not updating data correctly
- Fabric:
- Wrong mixin configuration (was only registered on the client, oops)
- Redstone wire not connecting to transmitters and receivers (if played on server)
- Frequency activated with remote stayed on if:
- Switching to another item in hotbar
- Dropped by player (if played on server)
- Normal usage (releasing right mouse button, if played on server)
- Forge (**1.20.4**):
- Minecraft startup crash with forge version of the mod (used invalid unobfuscated jar)
- Affected versions (**1.2.0**, **1.2.1**, **1.2.2**)
[1.3.0+1.20.4]: https://github.com/Razzokk/wireless-redstone/compare/v1.2.2+1.20.4...v1.3.0+1.20.4
### Added
- Attachment** block version of Redstone Transmitter/Receiver and P2P Redstone Transmitter/Receiver
- Configurable Attachment Mode: Define if the attachment block shall receive/output redstone only from/to the attached block or also all adjacent ones (except the opposite of the attached side)
- Target is shown underneath the crosshair when a P2P block is looked at with a **Linker**
- Frequency items show a message after a frequency has been copied or set
### Changed
- Receivers are now updated immediately after a transmitter is (un)powered (before: 1 redstone tick delay)
- This also allows to send 1 game ticks to receivers (e.g. with an observer)
- Use int array tag (NBT) for storing block positions (transmitters, p2p link, ...)
- This change is *only* backwards compatible (i.e., you can upgrade to newer versions but going back to older one will break the redstone network)
- Improved names and descriptions in config screen
- Redstone transmitters and receivers now also update directly after block placement (also with
/setblockand/fillcommand) - If you place a transmitter with a frequency (e.g., picked up in creative with CTRL, it also shows the frequency in the tooltip), it will now correctly register itself in the redstone ether network, before it did not do that
- If you place a receiver with a frequency it will turn on if any transmitters on the frequency are on
- Note: Frequency receivers (transmitters not) now also work when relocated with frames from project-red
### Fixed
- Sniffer stack size is supposed to be 1
- Sniffer and target highlight render wobbling when far out in the world due to floating point number precision (the farther out, the bigger the wobble)
- P2P transmitter and receiver block entities not updating data correctly
- Fabric:
- Wrong mixin configuration (was only registered on the client, oops)
- Redstone wire not connecting to transmitters and receivers (if played on server)
- Frequency activated with remote stayed on if:
- Switching to another item in hotbar
- Dropped by player (if played on server)
- Normal usage (releasing right mouse button, if played on server)
- Forge (**1.20.4**):
- Minecraft startup crash with forge version of the mod (used invalid unobfuscated jar)
- Affected versions (**1.2.0**, **1.2.1**, **1.2.2**)
[1.3.0+1.20.4]: https://github.com/Razzokk/wireless-redstone/compare/v1.2.2+1.20.4...v1.3.0+1.20.4
Backport from 1.3.0+1.20.1
[1.3.0+1.19.2]: https://github.com/Razzokk/wireless-redstone/compare/v1.19.2-1.1.2...v1.3.0+1.19.2
Backport from 1.3.0+1.20.1
[1.3.0+1.19.2]: https://github.com/Razzokk/wireless-redstone/compare/v1.19.2-1.1.2...v1.3.0+1.19.2
### Changed
- Shorten display name on [CurseForge](https://www.curseforge.com/minecraft/mc-mods/wirelessredstone) and [Modrinth]():
- before:
[<loader> <mc-version>] wirelessredstone-<mod-version>e.g. **[Forge 1.20.1] wirelessredstone-1.2.2** - now:
[<loader> <mc-version>] <mod-version> Wireless Redstonee.g. **[Forge 1.20.1] 1.2.2 Wireless Redstone**
### Fixed
- Linker highlight not showing when held in off-hand
[1.2.2+1.20.4]: https://github.com/Razzokk/wireless-redstone/compare/v1.2.1+1.20.4...v1.2.2+1.20.4
### Changed
- Shorten display name on [CurseForge](https://www.curseforge.com/minecraft/mc-mods/wirelessredstone) and [Modrinth]():
- before:
[<loader> <mc-version>] wirelessredstone-<mod-version>e.g. **[Forge 1.20.1] wirelessredstone-1.2.2** - now:
[<loader> <mc-version>] <mod-version> Wireless Redstonee.g. **[Forge 1.20.1] 1.2.2 Wireless Redstone**
### Fixed
- Linker highlight not showing when held in off-hand
[1.2.2+1.20.4]: https://github.com/Razzokk/wireless-redstone/compare/v1.2.1+1.20.4...v1.2.2+1.20.4
### Changed
- Shorten display name on [CurseForge](https://www.curseforge.com/minecraft/mc-mods/wirelessredstone) and [Modrinth]():
- before:
[<loader> <mc-version>] wirelessredstone-<mod-version>e.g. **[Forge 1.20.1] wirelessredstone-1.2.2** - now:
[<loader> <mc-version>] <mod-version> Wireless Redstonee.g. **[Forge 1.20.1] 1.2.2 Wireless Redstone**
### Fixed
- Linker highlight not showing when held in off-hand
[1.2.2+1.20.4]: https://github.com/Razzokk/wireless-redstone/compare/v1.2.1+1.20.4...v1.2.2+1.20.4
### Changed
- Shorten display name on [CurseForge](https://www.curseforge.com/minecraft/mc-mods/wirelessredstone) and [Modrinth]():
- before:
[<loader> <mc-version>] wirelessredstone-<mod-version>e.g. **[Forge 1.20.1] wirelessredstone-1.2.2** - now:
[<loader> <mc-version>] <mod-version> Wireless Redstonee.g. **[Forge 1.20.1] 1.2.2 Wireless Redstone**
### Fixed
- Linker highlight not showing when held in off-hand
- NeoForge: startup crash due to locked registry exception
[1.2.2+1.20.1]: https://github.com/Razzokk/wireless-redstone/compare/v1.2.1+1.20.1...v1.2.2+1.20.1
### Changed
- Shorten display name on [CurseForge](https://www.curseforge.com/minecraft/mc-mods/wirelessredstone) and [Modrinth]():
- before:
[<loader> <mc-version>] wirelessredstone-<mod-version>e.g. **[Forge 1.20.1] wirelessredstone-1.2.2** - now:
[<loader> <mc-version>] <mod-version> Wireless Redstonee.g. **[Forge 1.20.1] 1.2.2 Wireless Redstone**
### Fixed
- Linker highlight not showing when held in off-hand
- NeoForge: startup crash due to locked registry exception
[1.2.2+1.20.1]: https://github.com/Razzokk/wireless-redstone/compare/v1.2.1+1.20.1...v1.2.2+1.20.1
Back-port from **1.2.1+1.20.4**
[1.2.1+1.20.1]: https://github.com/Razzokk/wireless-redstone/compare/v1.20.1-1.1.3...v1.2.1+1.20.1
Back-port from **1.2.1+1.20.4**
[1.2.1+1.20.1]: https://github.com/Razzokk/wireless-redstone/compare/v1.20.1-1.1.3...v1.2.1+1.20.1
### Changed
- Remove exception stacktrace from config error log
[1.2.1+1.20.4]: https://github.com/Razzokk/wireless-redstone/compare/v1.2.0+1.20.4...v1.2.1+1.20.4
### Changed
- Remove exception stacktrace from config error log
[1.2.1+1.20.4]: https://github.com/Razzokk/wireless-redstone/compare/v1.2.0+1.20.4...v1.2.1+1.20.4
### Changed
- Remove exception stacktrace from config error log
[1.2.1+1.20.4]: https://github.com/Razzokk/wireless-redstone/compare/v1.2.0+1.20.4...v1.2.1+1.20.4
### Changed
- Versioning Scheme:
- Before:
<mcversion>-<version>, e.g.1.20.4-1.2.0 - After:
<version>+<mcversion>, e.g.1.2.0+1.20.4 - Dev only
- use [ParchmentMC](https://parchmentmc.org/) for mappings and adjust/re-write code accordingly
- refactor code to be more in common module
- improve project structure (multi-loader) with help of:
- [MultiLoader-Template](https://github.com/jaredlll08/MultiLoader-Template)
- [greenhouse-multiloader-template](https://github.com/GreenhouseModding/greenhouse-multiloader-template)
[1.2.0+1.20.4]: https://github.com/Razzokk/wireless-redstone/compare/v1.20.4-1.2.0-beta...v1.2.0+1.20.4
### Changed
- Versioning Scheme:
- Before:
<mcversion>-<version>, e.g.1.20.4-1.2.0 - After:
<version>+<mcversion>, e.g.1.2.0+1.20.4 - Dev only
- use [ParchmentMC](https://parchmentmc.org/) for mappings and adjust/re-write code accordingly
- refactor code to be more in common module
- improve project structure (multi-loader) with help of:
- [MultiLoader-Template](https://github.com/jaredlll08/MultiLoader-Template)
- [greenhouse-multiloader-template](https://github.com/GreenhouseModding/greenhouse-multiloader-template)
[1.2.0+1.20.4]: https://github.com/Razzokk/wireless-redstone/compare/v1.20.4-1.2.0-beta...v1.2.0+1.20.4
### Changed
- Versioning Scheme:
- Before:
<mcversion>-<version>, e.g.1.20.4-1.2.0 - After:
<version>+<mcversion>, e.g.1.2.0+1.20.4 - Dev only
- use [ParchmentMC](https://parchmentmc.org/) for mappings and adjust/re-write code accordingly
- refactor code to be more in common module
- improve project structure (multi-loader) with help of:
- [MultiLoader-Template](https://github.com/jaredlll08/MultiLoader-Template)
- [greenhouse-multiloader-template](https://github.com/GreenhouseModding/greenhouse-multiloader-template)
[1.2.0+1.20.4]: https://github.com/Razzokk/wireless-redstone/compare/v1.20.4-1.2.0-beta...v1.2.0+1.20.4
### Fixed
- Forge & NeoForge: redstone wires connecting up or down to transmitters/receivers
- Fabric: redstone wires connecting up or down to redstone utility blocks
### Added
- P2P redstone transmitter** and **receiver** for direct wireless linkage
- Linker** to link p2p transmitter and receiver
- Similar to the sniffer, highlights the targeted block
### Changed
- Redstone transmitters and receivers now use the
cube_columnblock model instead ofcube_bottom_top - Why? The bottom and top textures have been the same since the initial release,
- If you have a custom resource pack for Wireless Redstone, you can still use the
cube_bottom_topmodel,
- Highlight renderers now use the outline of the block instead of just a 1x1x1 block
[1.20.4-1.2.0-beta]: https://github.com/Razzokk/wireless-redstone/compare/release/1.20.4-1.1.5...release/1.20.4-1.2.0-beta
### Fixed
- Forge & NeoForge: redstone wires connecting up or down to transmitters/receivers
- Fabric: redstone wires connecting up or down to redstone utility blocks
### Added
- P2P redstone transmitter** and **receiver** for direct wireless linkage
- Linker** to link p2p transmitter and receiver
- Similar to the sniffer, highlights the targeted block
### Changed
- Redstone transmitters and receivers now use the
cube_columnblock model instead ofcube_bottom_top - Why? The bottom and top textures have been the same since the initial release,
- If you have a custom resource pack for Wireless Redstone, you can still use the
cube_bottom_topmodel,
- Highlight renderers now use the outline of the block instead of just a 1x1x1 block
[1.20.4-1.2.0-beta]: https://github.com/Razzokk/wireless-redstone/compare/release/1.20.4-1.1.5...release/1.20.4-1.2.0-beta
### Fixed
- Forge & NeoForge: redstone wires connecting up or down to transmitters/receivers
- Fabric: redstone wires connecting up or down to redstone utility blocks
### Added
- P2P redstone transmitter** and **receiver** for direct wireless linkage
- Linker** to link p2p transmitter and receiver
- Similar to the sniffer, highlights the targeted block
### Changed
- Redstone transmitters and receivers now use the
cube_columnblock model instead ofcube_bottom_top - Why? The bottom and top textures have been the same since the initial release,
- If you have a custom resource pack for Wireless Redstone, you can still use the
cube_bottom_topmodel,
- Highlight renderers now use the outline of the block instead of just a 1x1x1 block
[1.20.4-1.2.0-beta]: https://github.com/Razzokk/wireless-redstone/compare/release/1.20.4-1.1.5...release/1.20.4-1.2.0-beta
### Fixed
- Forge & NeoForge: race condition on client setup -> item property registration
- Dev only:
- Forge: not starting in dev environment (module conflicts)
[1.20.4-1.1.5]: https://github.com/Razzokk/wireless-redstone/compare/release/1.20.4-1.1.4...release/1.20.4-1.1.5
### Fixed
- Forge & NeoForge: race condition on client setup -> item property registration
- Dev only:
- Forge: not starting in dev environment (module conflicts)
[1.20.4-1.1.5]: https://github.com/Razzokk/wireless-redstone/compare/release/1.20.4-1.1.4...release/1.20.4-1.1.5
Skip for Fabric
### Fixed
- Forge: race condition on client setup -> item property registration
[1.20.1-1.1.3]: https://github.com/Razzokk/wireless-redstone/compare/release/1.20.1-1.1.2...release/1.20.1-1.1.3
Skip for Fabric
### Fixed
- Forge: race condition on client setup -> item property registration
[1.19.4-1.1.1]: https://github.com/Razzokk/WirelessRedstone/compare/release/1.19.4-1.1.0...release/1.19.4-1.1.1
Skip for Fabric
### Fixed
- Forge: race condition on client setup -> item property registration
[1.19.2-1.1.2]: https://github.com/Razzokk/WirelessRedstone/compare/release/1.19.2-1.1.1...release/1.19.2-1.1.2
Skip for Fabric
### Fixed
- Forge: race condition on client setup -> item property registration
[1.18.2-1.1.2]: https://github.com/Razzokk/WirelessRedstone/compare/release/1.18.2-1.1.1...release/1.18.2-1.1.2
### Fixed
- Sniffer not outputting message on newly created world (no redstone ether present)
### Added
- Show frequency of transmitters and receivers when picked up with nbt data
### Changed
- Updated german translation
- Moved block textures to their respective directories
- If you have a custom resource pack for Wireless Redstone, you have to move and rename them too
- Sniffer chat messages:
- Changed style of how block positions are shown in chat (can now also be adjusted in lang file)
- From:
There are no active transmitters on this frequency (<frequency>),
No active transmitters on frequency <frequency>- From:
Active transmitters on this frequency (<frequency>): <transmitters>,
Active transmitters on frequency <frequency>: <transmitters>- Dev only:
- Separate datagen sub-project
- Update architectury loom to 1.6
- Update changelog plugin to 2.2.0
- Update fabric loader and api to 0.15.10 and 0.97.0+1.20.4 respectively
- Update forge to 49.0.49
- Update neoforged to 20.4.233
[1.20.4-1.1.4]: https://github.com/Razzokk/wireless-redstone/compare/release/1.20.4-1.1.3...release/1.20.4-1.1.4