2008Choco
Assigned
Reported
MC-131420
Waterlogged blocks use full block hitbox, not that of the block itself
Duplicate
MC-123183
Cannot eat plantable items when looking at blocks
Fixed
MC-88881
Barrier blocks don't block burning
Works As Intended
MC-83206
Having an ender pearl in the second hand and right-clicking with a block while out of placement range throws the ender pearl
Works As Intended
MC-45783
You cannot kill the enderdragon with commands
Duplicate
MC-45431
Redstone Comparator clock bug (Renamed)
Duplicate
Comments
Still in snapshot 16w39a, confirmed
The redstone clock is too close to the command block and isn't receiving a redstone pulse
I am officially a genius... Ok so I found the issue and it was in fact NOT the command block at all. So see what I had done was used a comparator clock and since the command block was too close to the redstone, it wasn't actually receiving a redstone pulse. I suppose that this can be considered a bug aswell though... I'll put another snapshot of what I mean.
I did try it. That was the first thing I did to see if the command worked. It didn't... That's when I realized it was bugged.
Notice the "Deaths = 6" scoreboard on the side of my screen?
Maybe this snapshot will help you get a general idea of what I'm trying to explain.
I have added the scoreboard into the game with those stats, however the command is still not recognizing that I have 3 deaths. The exact command I used is
testfor @p[score_deaths_min=3]testfor @p[score_deaths_min=3]. I am aware that you need to have 3 deaths and that it tests for the nearest player and I have accomplished all of those listed criteria but it still does not output a signal.
Confirmed in 1.16.1 release.