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
.
Related issues
is duplicated by
Attachments
Comments


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.

Might be related to MC-50166, although the 2 issues are pretty far apart.

Confirmed for 1.8.1-pre2.

confirmed for 1.10 pre-2

Confirmed for 1.10.

Confirmed for 1.10.2

Confirmed for 1.11.2 and 17w06a
Was never actually fixed for /fill, reopening

can confirm this is still the case in 1.15.2

I got "Successfully filled 1 blocks" in 20w19a, yet this was never said to be fixed. I'll check 20w17a.

Confirmed 1.16.1 and 20w29a
Can confirm in 20w48a. I've attached a video of this happening to help people better understand/reproduce the issue.
Can confirm in 21w03a.
Can confirm in 21w05b.
Can confirm in 21w06a.
Can confirm in 21w07a. Video attached.
Can confirm in 21w11a.
Can confirm in 21w14a.
Can confirm in 21w17a.
Can confirm in 1.17.1.

Can confirm in 1.18.1.
Can confirm in 1.18.2 and 22w11a.
Can confirm in 1.19.
Can confirm in 1.19.2.

Can confirm for 23w04a.