Transmitter and Reciever Blocks

(I've seen similar ideas posted, but they're either narrow in scope, or go way beyond, so i'll post this.)

The idea in a nutshell:

2 new, craftable blocks. A transmitter block which is capable of transmitting a wireless signal when powered, and a reciever block which is powered when it recieves a wireless signal.

Given the simplicity of the idea, the ease in which it can be included, how well it fits with Minecraft's existing "electronic" dynamic, and the possibilities presented by such devices, i find it absolutely astonishing that it hasn't already been implemented. It *is* the next logical step in the progression of redstone logic.

Background:

So far in Minecraft, it is possible to create incredibly complex devices based upon the simple concept of redstone circuitry. I don't keep track, but are we at 64 bit CPU's yet? Regardless, everything that has been created so far is built upon and restricted by a simple rule: A signal must be conveyed along a redstone wire or input/output block, therefore the range of an electronic redstone signal is effectively 1 metre. Every electronic device built in minecraft
is built with cables, and those cables are 1 metre thick (and they don't bend well). Small wonder then that relatively simple circuits can occupy entire rooms, and complex applications can occupy the entire loading range of the game.

But what if there was a way to convey a signal across a distance greater than 1 metre? What if there was a way to convey a signal without the wires? Humans cracked this back in the 19th century and it revolutionised the world. Steve too could crack it and it would revolutionise Minecraft, if only the blocks were implemented...

The idea in detail:

The transmitter and reciever blocks are crafted at the workbench (it doesn't matter what from - that's beyond the scope of the article). By themselves, they do nothing. They are input/output blocks the same as switches and buttons, but unlike those blocks, they cannot be activated directly. They would be equivalent to the redstone torch. It's output state changing when its input changes. That's the idea at the most basic level, at least. With existing redstone circuitry, it's already possible to utilize every function and application of wireless tech with blocks that have only that basic function.

Alternatively, opting for a slightly more "refined" design, the blocks may also be implemented as configurable blocks, similar to the redstone repeater blocks and note blocks, with variable settings. The refined design would eliminate the need to build some of the circuitry required in the block's functions, exactly as the repeater block does. (That said, i'd be happy to have unconfigurable blocks, performing only that most basic function, if only it meant they'd be included.)

The transmitter block:

(basic design) When powered by a redstone source, will transmit a signal. A constant input equals a constant signal. A pulsed input transmits a pulsed signal. A "strongly powered" input (1 block from the power source) transmits a strong signal, and a weak input (15 blocks from power source) transmits a weak signal. The frequency is therefore customisable, based on the existing frequencies available from current redstone pulsers. The range of the signal is therefore customisable based on the length of existing redstone cables. The exact range? I don't know. That's something that can be worked out later, but given that there is already an existing and easy way of conveying a signal across a short distance, i'd say that range has to be large. Possibly even the entire loading range.

(possible refined design) Has right-clickable settings similar to the repeater block which may configure transmission frequencies and strengths, regardless of the frequency/strength of the input.

The reciever block:

(basic design) When is within range of a transmitted signal, will output power to immediately adjacent blocks, equal to the frequency of the signal (and possibly even equal to the strength of the signal, based on the range of the transmitted signal, or possibly the strength of the source powering the transmitter block.)

(refined design) Has right-clickable configuration settings which may enable the block to be powered only when it recieves a signal of the nominated frequency and/or strength.

And that's it. Nothing more to it, and there doesn't need to be. The practical applications are staggering.

Allow me to finish up with two thoughts:

Firstly, and simply, the next logical step after transmitter/reciever blocks may be the implementation of craftable, hand-held tools which either transmit or recieve a signal. Wrap your head around the further applications, if you will...

Secondly, somewhat paradoxically, real-world human circuit technology has advanced along a path of steadily reducing the size of the circuits by reducing the size of the cables. Since we can reduce cables far more than we can reduce wireless transmitters and recievers, these devices have been left out of the inner workings of cpu's and other highly complex circuits, and subsequently have not been an influential factor in the architectural/conceptual design and evolution of those circuits. But Minecraft is different...

Minecraft cables are 1 metre in diameter, and by definition, will never get any smaller. Imagine then what the inclusion of wireless tech to the inner workings will do for the evolution of advanced Minecraft circuit design... Every circuit in Minecraft so far is possible in the real world, but not the other way round. Imagine how thought and direction of real-world circuit evolution may be influenced when impossible cpu's become possible in Minecraft...

Transmitter and Reciever Blocks

#1

#2

#3

#4

#5

#6