Found this bug with /setblock and (Sticky)pistons.
Steps to reproduce:
1. place a redstone block anywhere.
2. place a temp block next to the redstone block for where your pistons are going to go.
3. use /setblock x y z minecraft:piston[facing=up] at the temp blocks x,y,z.
4. do step 3 again (at the same x,y,z) but change 'up' to east, west, north, south or down
when you do this you'll end up with a piston with 5 heads destroying any one of them will destroy the whole thing.
i was trying to use the /setblock for a 2 story maze and i ran into this, was expecting the previous piston(and piston head) to be replaced, not become a multi-headed piston. kinda broke my maze.
Environment
Computer Type: Desktop
OS: Windows 10 (x64) |
Java Version: 1.8.0(**) |
Processor: "AMD FX(tm)-6350 Six-Core Processor 3.90 GHz" |
Graphics Card: "NVIDIA GeForce GTX 1060 6GB (GP106) @ 253 MHz" |
RAM: 16GB (ram given to minecraft 7-11GB) |
Screen Res.: 1920x1080 |
(**) I don't know if this matters anymore
For future reports, please make your screenshots properly lit, if possible.