Timothy Hynes
Assigned
Reported
Comments
Okay, I think the problem is only with stat.useItem. stat.mineBlock seems to work fine for anything other than Grass, it works with Stone which does not drop itself and cobble which does though.
Actually I just tested stat.mineBlock.3 (dirt) and it worked fine. I did delete the first objective (Mine Stone) but it didn't effect Grass. It may have to do with the fact the Grass blocks drop dirt, not themselves. I will continue testing and post any updates here.
Ah, okay. It should at least clear the previous output box though.
Yes, that is it.
The screenshot shows the message within the "Previous Output" box, but the command block worked fine.
I was typing the description, sorry about that.
I think is more of a feature suggestion than a bug but yes that would be nice.
There could be practical uses of the current state though.
If a minecart goes slowly over an activator rail will it still be triggered multiple times, even at once every 4 ticks?
Sorry if I confused anyone, I mean it may have to do with the addition of minecarts with command blocks, I understand they were not involved directly. I mean from a coding perspective perhaps that was the problem.
I attached the screenshot from my report to keep them all in one place.
This may have something to do with the Minecarts with Command Blocks, it makes sense for them to say that because they cannot be connected to a comparator.
Sorry about the clone, I searched first but I must have typed something wrong.
This command block was attached to a hopper clock and as you can see behaved as if a player had used the command, not a command block.
The command block stated "[14:00:25] /testfor is only usable by commandblocks with analog output" within the "previous output" box.
f4 disables shaders as well, right?
I have the same problem, in the screenshot I typed "/gamerule commandBlockOutput" then placed some blocks via command block and as you can see it still broadcast the messages anyway. Please fix soon.
I have the same issue, it seems that bats drop 0-2 tile.air.name blocks on death.
I uploaded a screenshot of the window. As you can see I have the same problem on an entirely different OS.
Fov is not normally consistent around the edges. This may be due to the fact that the blocks appear closer around the edges as well.
Sorry for the constant changes but now stat.useItem.276 (Diamond Sword) works. I have no idea what the problem is but I do know that stat.useItem.383 works and many other items (Eggs, Endereyes, Snowballs, Fishing Rods and bows) do not work.