i was doing some funny stuff with the new redstone block when i suddenly encountered a way to totally remove the redstoneblock.
reproduce: start off with creating the setup as shown in the image: 2013-02-09_12.49.34
then place redstone wire on top of the block, and it will disappear all the sudden.
the other screenshot shows exactly what happens, the redstone block instantly gets pushed away by the next piston, and then it is gone.
other notable bugs: when you wouldnt use this quartz block and would keep the wires on 1 layer the redstoneblock will be moving around in circles(as expected) but the wires wont be powered, while without the wires it wont move around(or atleast it didnt when i tried). Even more strange is that when i make a screenshot while the redstone block is moving around, it disappears aswell(this is with the redstone wire on the same level, as shown in my last screenshot, after this screenshot the redstone block had disappeared aswell)
greetings,
Quimtoh
Related issues
duplicates
Attachments
Comments


Loooool, I didnt even notice the redstone block still somehow was in the circuit, as you can see the pistons are still being moved but the redstoneblock is no longer visible. <- this was only about the seccond bug, the one with the redstone wire on the same level as the pistons.
2nd note to this is that when interrupting one of the wires the block will reappear, this did not happen with the first bug I noted, and in my opinion is a glitch even if it doesn't really disappear but just gets invisible.

repeaters can solve all issues, therefore i think pistons HAVE to get a delay in order to solve this, because otherwise there is just no simple way i can see which solves the problem.

repeaters solve the issues that occurred, it is now even possible to place a second block in the circuit without having a chance for the blocks to disappear. also it is of course much easier to time the placement so that the block doesn't push away any wires

Thus bug is a duplicate of MC-5774

...please use the search function to see if your bug has already been submitted. Currently over 51% of tickets are being closed as duplicate.

Yeah if people would make a GOOD summary it would be possible, but in this case I thought it was a redstoneblock SPECIFIC bug, sorry for that but really, how am I supposed to know if this bug is redstoneblock specific or not?

the list with piston related bugs is so huge that i indeed use the search function and type: redstoneblock disappears as search function.... well that didnt give a hit obviously.

You should try a few different search queries before filing a bug. "redstone block disappearing" or "redstone block disappears" (with space between redstone and block) will find dozens of bugs most of which are already marked as duplicate of MC-5774.