Also affects rails.
Does indeed appear to be caused by cactus not wanting to exist beside moving_piston
.
The cactus does not break when a rod/rail is 0-ticked into adjacency or moved out of adjacency as mentioned above; both are situations where no moving_piston
is created beside the cactus (and exists for more than one tick).
Duplicate of MC-153385