MuellMark
commented
2 years ago Added a diamond block under the piston that is pushed down after the button is pressed. The code then reads for a diamond one block lower, instead of the piston head. Once the diamond is read, it evolves the next generation of shapes, just like it did with the piston head.
Right now, a button pushes a piston down, and said piston head is read in to indicate when to move on to the next generation. However, especially when dealing with evolving block lists, the piston could come back up before it can be read. This should be fixed, and one way to try is by pushing a block down with a non-sticky piston. That way when the loop comes back to reading whether or not to advance, the block is read in, not the piston head