This is a fork of MC-119523, as the behaviour has changed, but is still not as expected.
Now (so far as I can tell) using a piston to push or pull certain blocks into adjacency with a cactus will always break the cactus. Exiting adjacency no longer has this effect
However you can still place these blocks next to cactus without breaking the cactus, (and you can still place cactus next to them)
Affected blocks include: end rods, wool carpets and rails
End rod orientation continues to have no effect.
Linked issues
is duplicated by 1
relates to 2
Comments 7
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).
Relates to [MC-161026]
Only seems to happen when pushing/pulling end rods into adjacency of a cactus, not when pushing/pulling it away.