Minecraft – How to make a reliable and compact random timer

Since there is no answer I will show how to make a random unit:

If you are not ready to have your mind blown go to conclusion at the end.

Take a 3-clock unit and set an output somewhere, now since this is only 3-clock it's gonna burn at RANDOM place so the output will be random. Like this:

Now you probably don't want it to change so much but only when it stopped, well.. idk if anyone used it(probably used), anyway I've made it my self, I call it "signal cuter" the point is to split the signal into 2 signals: first contain odd number of "not gates" and the second even, and then merge them into "or gate", the result is: when a signal is sent, it's gonna stay as the output until the second path will cut the signal and that way no matter for how long you set the input to "on", the output gonna be "on" only for length(second path) - length(first path) "ticks".

in this example, all signals that are more then 3 ticks length are shorted to 3 ticks long. On same property you can make a "signal protector" also made by me :), it's not passing signals less than X long all the difference is that both paths first and second need to be odd length and the X is equal to length(second path) - length(first path), but the signal become shorter then the original signal length. Example:

FINALLY the conclusion: so now you can take the a 3-clock and to chain it with the "signal protector" with X=2 and THIS WILL BE STABLE!! It won't throw junk until the 3-clock burned and the result is stable, the next random will be generated after the next 3-clock burn, if you want to make it faster just make many units of that.

THE RESULT:

It's still throw junk in "Redstone Simulator" but in "Minecraft" this works great! Please if you're passing on this technique, leave the names "Signal Cutter" and "Signal Protector".

The circuitry behind this is fairly simple. It relies on the principle that the default state of a Redstone Torch is on, and that when power is applied to the block that it is mounted on, it will turn off. When no power is applied to the bottom block in the circuit, the bottom and top Redstone Torches are on, and the middle is off, because the bottom one is powering the block the middle one is attached to.

The bottom piston is on because the bottom Redstone Torch is powering it. The middle piston is also on, because the bottom Redstone Torch is powering the cobblestone directly above it, also powering the piston adjacent. The top piston is on because the top Redstone Torch is powering it.

When a current is applied to the bottom block of cobblestone, the bottom Redstone Torch is turned off, because it is mounted on the cobblestone. This makes the bottom piston retract. Because no power is being applied to the middle cobblestone block, the middle piston turns off, and the middle Redstone Torch also turns on (because power isn't being applied to it anymore). This, in turn, turns off the top Redstone Torch (because power is being applied to the cobblestone block it is mounted on), turning the top piston off.

And yes, this design can be repeated upwards infinitely (but there will be a noticeable delay between the topmost and bottommost pistons, as it takes time for each Redstone Torch to change states).