To reproduce, run /fill ~ ~-1 ~ ~ ~-1 ~ air destroy
, where the affected block is not already air. The block will be destroyed as expected, but the error message "No blocks were filled" will appear. The command's result
and success
values will both be zero.
No longer affects /setblock
.
Linked issues
is duplicated by 6
Attachments
Comments 25
Might be related to MC-50166, although the 2 issues are pretty far apart.
Confirmed but this seems to only be displayed if you use "air 0 destroy". If you type the command as just "air" it will display properly. And if you type the command as "sandstone 0 destroy" it will also display properly. I'd clarify the bug title a bit more to explain it's wioth the "air 0 destroy" that is messing up.