Reproduce the steps:
1. Create the setup shown below
2. Test as labeled in the figure below.
3. After pulling the signal source marked RANDOM in the figure below, the piston will extend at random.
The expected behavior is that after pulling the signal source marked RANDOM in the figure below, the piston that always extends is the left piston.
Note that the redstone torch itself does seem like it is setting a "front" direction when powering a redstone dust above it, but it doesn't when the dust is below.
Attachments
Comments 4
Since the upper torch points in the opposite direction, its local "left" should actually point into the piston that you labeled as "right". But even in that case, the behavior should still be deterministic, as opposed to the observed randomness.
Also, the same bug applies not only to torches but also to buttons. In the given setup, you can replace the upper torch with either a button that hangs on that same wall (which makes the game ignore the button's rotation and randomize the outcome), or replace that same torch with a block and place a floor button on top of that block (which makes the wire accurately respond to the button's rotation)
From checking the 24w34a changelog, redstone has a left preference when the redstone is not coming from above. In your example, the power is coming from above:
Redstone wire updates now have a left-first preference
That means if there is a fork in a wire and the distance on both sides is the same, the left side will be updated first
This removes most of the random behavior
The remaining edge cases which are still random are situations where wire gets powered from above or below without enough context
@@unknown This is a bug; the redstone torch does give enough context to determine a direction in this case, as it does have something that can be considered "front".
If this was a pressure plate for example, it would be WAI, but any block like the wall redstone torch which can be rotated in all 4 cardinal directions should not be random anymore.
[^$ZTBJ7(CSFAD}7[UPO56)J5.png]
[media][media][media][media]