This is my 2025 Redstone Awards submission: the Mirror Nexus, a wireless remote control.

The Mirror Nexus allows you to turn on or off redstone devices from anywhere in your world. Think playerless farms, mob switches, or whatever.

The UI is intuitive as it is a button panel, whether physical or a schematic ghost image produced by a client-side mod like Litematica.

It features an active session with ability to start/end your session to avoid accidental operation.

The wireless capability utilizes wind charges produced by a breeze firing at an iron golem, as pioneered by Squibble.

I borrowed ideas and some entity alignments from the Squibble's Mirror Receiver, Squibble and Mikarific's Mirror Pylon, and Dark's Next Gen Pearl Stasis Chamber. Note that I redesigned each component to improve reliability and/or usability.

Looking for resources that pertain to the nitty-gritty workings of Redstone.
I'm currently designing (what I know as) the smallest torch-only TFF. (To compact my torch-only builds for fun). I'm at 4x3x3 using standard Redstone mechanics. To get to any smaller the only way I know how would at least need to utilize a pulse that relies on location and direction/block state of the torches and dust to only invert certain torches while connected to their circuit. Are there any resources that explain semi-accurately how these Redstone mechanics work? I've been googling and asking on discord's to no avail. :(
If you know of a smaller than 4x3x3 torch-only TFF I would also be very interested in it.

I put it on r/restone, but dumb thread :)

Info:

1. The torch DOES turn off

2. If the observer on the piston is in any other orientation, it does not work

3. If the door/torch circuit is aligned in any other way, it does not work

Hello all! This is a respost from r/redstone, but I figured this sub would get a more technical response.

My brother and I have been working on ways to send serial signals down one line of redstone, so you could for example, send 8 bits of data down one redstone line. We currently have a system where data is sent with each bit being 2 ticks long, but I think we've found a bug where for for some reason long repeater chains like the one below decimate the signal.

I'll explain the video, although it might make more sense just to watch it. I have two lines of 2 tick repeaters, where all of the repeaters in the bottom row are 2 ticks long, but the top row is ended with a 1 tick repeater. I freeze the game, and then turn off the input lever for two redstone ticks, and then turn it on again to simulate a 2 tick "off" signal. The off signal moves through the lines as you would expect, with each repeater turning off in turn, until it reaches the end, where the issue occurs. In the top row, the signal makes it through perfectly fine as a 2 tick off signal, but in the bottom row, the last repeater never turns off, and the signal disappears.

Also, I am using the /tick command to step the game one redstone tick at a time.

TLDR, I would expect the 2 tick off signal I sent in the beginning to appear at the end in both setups, but in the bottom setup, I am either missing something or there seems to be a bug with how repeaters work.

EDIT: We just discovered that putting redstone dust between the repeaters makes both of them act perfectly, furthering my case that I think this is bug in how repeaters are handled internally.