MC v 1.19.4 fabric 0.14.23 Mod v 2.4.15-fabric (moonlight 2.4.16-fabric)

I personally don't consider this a bug, but a feature. However, you are the developer, you decide what to be and what not.

We know that the relayer can't see the signal on a normal (full) block. But if the block is placed and gets a signal at the same time,

• the relayer will see that signal (strong or weak). And moreover - it saves it! You can turn off the signal on the block.

That state is inert to other signals, leaving the world or game. Also, is inert to other block updates around. But if you break the block or move it, or move a relayer, the stored signal is gone.

If the stored signal disappeared in 0-tic time, this might be more useful..... I have not been able to test this in game. I've tried it, but no success. But I got results from which I can tell that the relayer shuts down around 1-tick time. Always.

screenshots:

It turns out that in order to catch a signal, relayer must see not only the signal, but also the block update. Normal blocks won't update from a signal unless they are placed, moved, or broken. And that's not a bug, is it?!

Yeah it's a bug. It's meant to copy whatever singla that target block has. Works on place but doesn't get the proper block update it seems. Idk if that's a useful thing to have, if not I'll try to fix

This can be useful. We can dynamically store the signal, also with its level. ! Composters will lose here, they can be filled automatically, but it's more complicated and longer.
I think it would be good for code locks on redstone. Or other mechanisms that depend on the order of the input signals.
And, relayer can be moved, so, you can move your memory)))

hm ill leave this open. guess ill keep it as a sort of feature for now