Caty Lawren

Still in 19w07a

Confirmed on 18w47b

Confirmed for 18w46a.

@Skylinerw This is not a clone. This is an entirely different thing. The other report is about usage being repeated, while this is about a legitimate (while minor) performance issue.

@redstonehelper The bug is not that we can't do it. The bug is that MC is giving a weird error message that should be more clear.

Only happens when the bottom of your hitbox is covered, not the top. You can test that by making a 1-deep hole in the ground and replacing a side of the hole with a fence, pushing a block over your head with a piston, and going into 3rd-person mode and looking around until you can see the sky. It's bright as ever.

Confirmed for 1.9 Release.

I don't see how it would be intended for this to happen. It's a syntax error. It should only fail once, because there is only one command with one error. Wouldn't evaluating a bad command many times still be considered a bug?

15w45a, and way more easily noticeable with the new Elytra. Flying into a wall that has a one-tall hole, and hitting that hole, will cause you to instantly go to first-person view. Really annoying.

Confirmed existent in 15w36e and fixed in 15w37a.

It's not fixed! Confirmed on 15w36d! How can you claim it's fixed when it's so easily reproducible?

Steps:
Place a command block (No need to enter a command. All three varieties work.)
Die by either command, or by going into survival and dying naturally.
Try to open command block. (Even in creative mode, it won't work.)
Fail miserably.
Proceed to hate bugs.

I could not reproduce the crash, but the bug is there. 15w36d.

Confirmed for 15w36d. Armor stands turn invisible, and executing a command or using testfor proves their existence. I went to the nether a few times, and some in one chunk were invisible, while others in a different chunk were still there. Ughghghg.

Edit0: All chunks are spawn chunks.

I was about to post this myself, until I saw it here. Confirmed for 15w35e. Please fix this. I need a marker that is detectable.

The 'comparator bug' from one of the duplicates is actually not a bug. The redstone directly at the output and the redstone next to that one always stay on, as the comparator is in 'subtractive mode' and is subtracting it's output from it's primary input. Because the output is diminished by the distance at which it reaches the secondary input, it subtracts two less than the primary input from the primary input, leaving a value of two. That value diminishes to zero from the distance to the secondary input, which is subtracted from the value at the primary input, making the output equal to the primary input, which was the starting state. This cycle then repeats until it is interrupted.