MC-78780/fill hollow and destroy calculates number of blocks incorrectly
This is probably caused by a unknown fix of MC-58297 or because of the seconds part of this report
hollow mode not counting placed air blocks in middle
The hollow mode calculates the block count like the outline mode, which can be incorrect if air blocks are placed in the middle
How to reproduce
- /fill ~1 ~ ~1 ~3 ~2 ~3 glass 0 hollow
- Place a block at the free spot in the center
- Run the 1. command again
It will show that no blocks were changed, but it actually removed the block in the middle.
This can cause quite some problems if you use the /stats command in combination with it (it will shows the wrong block count).
The reason
The following is based on decompiled version of Minecraft 1.9 using MCP 9.24 beta. All method and class names are the names used in the decompiled version.
The reason why this happens is because the method net.minecraft.command.CommandFill.execute(MinecraftServer, ICommandSender, String[]) only tries to set air in the middle but does increase the modified blocks count in case it was successful.
if (args[8].equals("hollow")) { // Replaced this //world.setBlockState(blockpos4, Blocks.air.getDefaultState(), 2); //list.add(blockpos4); if (world.setBlockState(blockpos4, Blocks.air.getDefaultState(), 2)) { list.add(blockpos4); j++; } }
destroy not working with air as block to be placed
The destroy mode is not counting placed air blocks, this is not the case for the /setblock command
How to reproduce
- Stand on a block
- /fill ~ ~-1 ~ ~ ~-1 ~ air 0 destroy
"No blocks filled" is definitely wrong here, because it destroyed that block
The reason
The following is based on decompiled version of Minecraft 1.9 using MCP 9.24 beta. All method and class names are the names used in the decompiled version.
The reason why this happens is because the method net.minecraft.command.CommandFill.execute(MinecraftServer, ICommandSender, String[]) first destroys the block which means that at this position is air and then later tries to replace the block with air which returns that the block could not be placed.
if (args[8].equals("destroy")) { // Replaced this //world.destroyBlock(blockpos4, true); if (world.destroyBlock(blockpos4, true) && block == Blocks.air) { list.add(blockpos4); j++; continue; } }
Created Issue:
fill hollow calculates number of blocks incorrectly
This is probably caused by a unknown fix of
MC-58297The hollow mode calculates now the block count like the outline mode, which can be uncorrect:
1. /fill ~1 ~ ~1 ~3 ~2 ~3 glass 0 hollow
2. Place a block (not glass) at the free spot in the centre
3. Run the 1. command againIt will show that no blocks were changed, but it actually removed the block in the middle.
This can cause quite some problems if you use the /stats command in combination with it (it will shows the wrong block count).
fill hollow and destroy calculates number of blocks incorrectly
This is probably caused by a unknown fix of
MC-58297The hollow mode calculates now the block count like the outline mode, which can be uncorrect:
1. /fill ~1 ~ ~1 ~3 ~2 ~3 glass 0 hollow
2. Place a block (not glass) at the free spot in the centre
3. Run the 1. command againIt will show that no blocks were changed, but it actually removed the block in the middle.
This can cause quite some problems if you use the /stats command in combination with it (it will shows the wrong block count).This is probably caused by a unknown fix of
MC-58297or because of the seconds part of this report
- The hollow mode calculates now the block count like the outline mode, which can be uncorrect:
1. /fill ~1 ~ ~1 ~3 ~2 ~3 glass 0 hollow
2. Place a block (not glass) at the free spot in the centre
3. Run the 1. command againIt will show that no blocks were changed, but it actually removed the block in the middle.
This can cause quite some problems if you use the /stats command in combination with it (it will shows the wrong block count).
This is probably caused by a unknown fix of
MC-58297or because of the seconds part of this report
- The hollow mode calculates now the block count like the outline mode, which can be uncorrect:
1. /fill ~1 ~ ~1 ~3 ~2 ~3 glass 0 hollow
2. Place a block (not glass) at the free spot in the centre
3. Run the 1. command againIt will show that no blocks were changed, but it actually removed the block in the middle.
This can cause quite some problems if you use the /stats command in combination with it (it will shows the wrong block count).This is probably caused by a unknown fix of
MC-58297or because of the seconds part of this report
- The hollow mode calculates now the block count like the outline mode, which can be uncorrect:
1. /fill ~1 ~ ~1 ~3 ~2 ~3 glass 0 hollow
2. Place a block (not glass) at the free spot in the centre
3. Run the 1. command again
It will show that no blocks were changed, but it actually removed the block in the middle.
This can cause quite some problems if you use the /stats command in combination with it (it will shows the wrong block count).
This is probably caused by a unknown fix of
MC-58297or because of the seconds part of this report
- The hollow mode calculates now the block count like the outline mode, which can be uncorrect:
1. /fill ~1 ~ ~1 ~3 ~2 ~3 glass 0 hollow
2. Place a block (not glass) at the free spot in the centre
3. Run the 1. command again
It will show that no blocks were changed, but it actually removed the block in the middle.
This can cause quite some problems if you use the /stats command in combination with it (it will shows the wrong block count).- The destroy mode with air calculates also the result wrong (! only with fill):
1. Stand on a block
2. /fill ~ ~-1 ~ ~ ~-1 ~ air 0 destroy
"No blocks were changed" is definitely wrong here, because it destroyed that block
This is probably caused by a unknown fix of
MC-58297or because of the seconds part of this report
- The hollow mode calculates now the block count like the outline mode, which can be uncorrect:
1. /fill ~1 ~ ~1 ~3 ~2 ~3 glass 0 hollow
2. Place a block (not glass) at the free spot in the centre
3. Run the 1. command again
It will show that no blocks were changed, but it actually removed the block in the middle.
This can cause quite some problems if you use the /stats command in combination with it (it will shows the wrong block count).- The destroy mode with air calculates also the result wrong (! only with fill):
1. Stand on a block
2. /fill ~ ~-1 ~ ~ ~-1 ~ air 0 destroy
"No blocks were changed" is definitely wrong here, because it destroyed that blockThis is probably caused by a unknown fix of
MC-58297or because of the seconds part of this report
- The hollow mode calculates now the block count like the outline mode, which can be uncorrect:
1. /fill ~1 ~ ~1 ~3 ~2 ~3 glass 0 hollow
2. Place a block (not glass) at the free spot in the centre
3. Run the 1. command again
It will show that no blocks were changed, but it actually removed the block in the middle.
This can cause quite some problems if you use the /stats command in combination with it (it will shows the wrong block count).
- The destroy mode with air calculates also the result wrong (! only with fill):
1. Stand on a block
2. /fill ~ ~-1 ~ ~ ~-1 ~ air 0 destroy
"No blocks were changed" is definitely wrong here, because it destroyed that block
This is probably caused by a unknown fix of
MC-58297or because of the seconds part of this report
- The hollow mode calculates now the block count like the outline mode, which can be uncorrect:
1. /fill ~1 ~ ~1 ~3 ~2 ~3 glass 0 hollow
2. Place a block (not glass) at the free spot in the centre
3. Run the 1. command again
It will show that no blocks were changed, but it actually removed the block in the middle.
This can cause quite some problems if you use the /stats command in combination with it (it will shows the wrong block count).
- The destroy mode with air calculates also the result wrong (! only with fill):
1. Stand on a block
2. /fill ~ ~-1 ~ ~ ~-1 ~ air 0 destroy
"No blockswere changed" is definitely wrong here, because it destroyed that blockThis is probably caused by a unknown fix of
MC-58297or because of the seconds part of this report
- The hollow mode calculates now the block count like the outline mode, which can be uncorrect:
1. /fill ~1 ~ ~1 ~3 ~2 ~3 glass 0 hollow
2. Place a block (not glass) at the free spot in the centre
3. Run the 1. command again
It will show that no blocks were changed, but it actually removed the block in the middle.
This can cause quite some problems if you use the /stats command in combination with it (it will shows the wrong block count).
- The destroy mode with air calculates also the result wrong (! only with fill):
1. Stand on a block
2. /fill ~ ~-1 ~ ~ ~-1 ~ air 0 destroy
"No blocks filled" is definitely wrong here, because it destroyed that block
This is probably caused by a unknown fix of
MC-58297or because of the seconds part of this report
- The hollow mode calculates now the block count like the outline mode, which can be uncorrect:
1. /fill ~1 ~ ~1 ~3 ~2 ~3 glass 0 hollow
2. Place a block (not glass) at the free spot in the centre3.Run the 1. command again
It will show that no blocks were changed, but it actually removed the block in the middle.
This can cause quite some problems if you use the /stats command in combination with it (it will shows the wrong block count).
- The destroy mode with air calculates also the result wrong (! only with fill):
1. Stand on a block
2. /fill ~ ~-1 ~ ~ ~-1 ~ air 0 destroy
"No blocks filled" is definitely wrong here, because it destroyed that blockThis is probably caused by a unknown fix of
MC-58297or because of the seconds part of this reporthollow mode not counting placed air blocks in middle
The hollow mode calculates the block count like the outline mode, which can be uncorrect if air blocks are placed in the middle
How to reproduce
- /fill ~1 ~ ~1 ~3 ~2 ~3 glass 0 hollow
- Place a block (not glass) at the free spot in the centre
- Run the 1. command again
It will show that no blocks were changed, but it actually removed the block in the middle.
This can cause quite some problems if you use the /stats command in combination with it (it will shows the wrong block count).The reason
The following is based on decompiled version of Minecraft 1.9 using MCP 9.24 beta. All method and class names are the names used in the decompiled version.
destroy not working with air as block to be placed
The destroy mode is not counting placed air blocks, this is not the case for the /setblock command
How to reproduce
- Stand on a block
- /fill ~ ~-1 ~ ~ ~-1 ~ air 0 destroy
"No blocks filled" is definitely wrong here, because it destroyed that blockThe reason
This is probably caused by a unknown fix of
MC-58297or because of the seconds part of this reporthollow mode not counting placed air blocks in middle
The hollow mode calculates the block count like the outline mode, which can be uncorrect if air blocks are placed in the middle
How to reproduce
- /fill ~1 ~ ~1 ~3 ~2 ~3 glass 0 hollow
- Place a block
(not glass)at the free spot in the centre- Run the 1. command again
It will show that no blocks were changed, but it actually removed the block in the middle.
This can cause quite some problems if you use the /stats command in combination with it (it will shows the wrong block count).The reason
The following is based on decompiled version of Minecraft 1.9 using MCP 9.24 beta. All method and class names are the names used in the decompiled version.
destroy not working with air as block to be placed
The destroy mode is not counting placed air blocks, this is not the case for the /setblock command
How to reproduce
- Stand on a block
- /fill ~ ~-1 ~ ~ ~-1 ~ air 0 destroy
"No blocks filled" is definitely wrong here, because it destroyed that blockThe reason
This is probably caused by a unknown fix of
MC-58297or because of the seconds part of this reporthollow mode not counting placed air blocks in middle
The hollow mode calculates the block count like the outline mode, which can be uncorrect if air blocks are placed in the middle
How to reproduce
- /fill ~1 ~ ~1 ~3 ~2 ~3 glass 0 hollow
- Place a block at the free spot in the centre
- Run the 1. command again
It will show that no blocks were changed, but it actually removed the block in the middle.
This can cause quite some problems if you use the /stats command in combination with it (it will shows the wrong block count).The reason
The following is based on decompiled version of Minecraft 1.9 using MCP 9.24 beta. All method and class names are the names used in the decompiled version.
The reason why this happens is because the method net.minecraft.command.CommandFill.execute(MinecraftServer, ICommandSender, String[]) only tries to set air in the middle but does increase the modified blocks count in case it was successful.
if (args[8].equals("hollow")) { // Replaced this //world.setBlockState(blockpos4, Blocks.air.getDefaultState(), 2); //list.add(blockpos4); if (world.setBlockState(blockpos4, Blocks.air.getDefaultState(), 2)) { list.add(blockpos4); j++; } }destroy not working with air as block to be placed
The destroy mode is not counting placed air blocks, this is not the case for the /setblock command
How to reproduce
- Stand on a block
- /fill ~ ~-1 ~ ~ ~-1 ~ air 0 destroy
"No blocks filled" is definitely wrong here, because it destroyed that blockThe reason
The following is based on decompiled version of Minecraft 1.9 using MCP 9.24 beta. All method and class names are the names used in the decompiled version.
The reason why this happens is because the method net.minecraft.command.CommandFill.execute(MinecraftServer, ICommandSender, String[]) first destroys the block which means that at this position is air and then later tries to replace the block with air which returns that the block could not be placed.
if (args[8].equals("destroy")) { // Replaced this //world.destroyBlock(blockpos4, true); if (world.destroyBlock(blockpos4, true) && block == Blocks.air) { list.add(blockpos4); j++; continue; } }
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
/fill hollow and destroy calculates number of blocks incorrectly
Is this still an issue in the most recent versions (currently that is 1.10.2, or 16w42a) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time. If you are the owner/reporter of this ticket, you can modify the affected version(s) yourself.
This is probably caused by a unknown fix of
MC-58297or because of the seconds part of this reporthollow mode not counting placed air blocks in middle
The hollow mode calculates the block count like the outline mode, which can be
uncorrect if air blocks are placed in the middleHow to reproduce
- /fill ~1 ~ ~1 ~3 ~2 ~3 glass 0 hollow
- Place a block at the free spot in the cent
re- Run the 1. command again
It will show that no blocks were changed, but it actually removed the block in the middle.
This can cause quite some problems if you use the /stats command in combination with it (it will shows the wrong block count).The reason
The following is based on decompiled version of Minecraft 1.9 using MCP 9.24 beta. All method and class names are the names used in the decompiled version.
The reason why this happens is because the method net.minecraft.command.CommandFill.execute(MinecraftServer, ICommandSender, String[]) only tries to set air in the middle but does increase the modified blocks count in case it was successful.
if (args[8].equals("hollow")) { // Replaced this //world.setBlockState(blockpos4, Blocks.air.getDefaultState(), 2); //list.add(blockpos4); if (world.setBlockState(blockpos4, Blocks.air.getDefaultState(), 2)) { list.add(blockpos4); j++; } }destroy not working with air as block to be placed
The destroy mode is not counting placed air blocks, this is not the case for the /setblock command
How to reproduce
- Stand on a block
- /fill ~ ~-1 ~ ~ ~-1 ~ air 0 destroy
"No blocks filled" is definitely wrong here, because it destroyed that blockThe reason
The following is based on decompiled version of Minecraft 1.9 using MCP 9.24 beta. All method and class names are the names used in the decompiled version.
The reason why this happens is because the method net.minecraft.command.CommandFill.execute(MinecraftServer, ICommandSender, String[]) first destroys the block which means that at this position is air and then later tries to replace the block with air which returns that the block could not be placed.
if (args[8].equals("destroy")) { // Replaced this //world.destroyBlock(blockpos4, true); if (world.destroyBlock(blockpos4, true) && block == Blocks.air) { list.add(blockpos4); j++; continue; } }This is probably caused by a unknown fix of
MC-58297or because of the seconds part of this reporthollow mode not counting placed air blocks in middle
The hollow mode calculates the block count like the outline mode, which can be incorrect if air blocks are placed in the middle
How to reproduce
- /fill ~1 ~ ~1 ~3 ~2 ~3 glass 0 hollow
- Place a block at the free spot in the center
- Run the 1. command again
It will show that no blocks were changed, but it actually removed the block in the middle.
This can cause quite some problems if you use the /stats command in combination with it (it will shows the wrong block count).The reason
The following is based on decompiled version of Minecraft 1.9 using MCP 9.24 beta. All method and class names are the names used in the decompiled version.
The reason why this happens is because the method net.minecraft.command.CommandFill.execute(MinecraftServer, ICommandSender, String[]) only tries to set air in the middle but does increase the modified blocks count in case it was successful.
if (args[8].equals("hollow")) { // Replaced this //world.setBlockState(blockpos4, Blocks.air.getDefaultState(), 2); //list.add(blockpos4); if (world.setBlockState(blockpos4, Blocks.air.getDefaultState(), 2)) { list.add(blockpos4); j++; } }destroy not working with air as block to be placed
The destroy mode is not counting placed air blocks, this is not the case for the /setblock command
How to reproduce
- Stand on a block
- /fill ~ ~-1 ~ ~ ~-1 ~ air 0 destroy
"No blocks filled" is definitely wrong here, because it destroyed that blockThe reason
The following is based on decompiled version of Minecraft 1.9 using MCP 9.24 beta. All method and class names are the names used in the decompiled version.
The reason why this happens is because the method net.minecraft.command.CommandFill.execute(MinecraftServer, ICommandSender, String[]) first destroys the block which means that at this position is air and then later tries to replace the block with air which returns that the block could not be placed.
if (args[8].equals("destroy")) { // Replaced this //world.destroyBlock(blockpos4, true); if (world.destroyBlock(blockpos4, true) && block == Blocks.air) { list.add(blockpos4); j++; continue; } }
![[Mod] redstonehelper](../../../data/avatars/users/10122.svg){kind=small}
Well, physically, it just changed it to air, and I don't think air is counted, thus making it as 'No blocks were changed'?
Well there is another bug with the /fill command with air and the destroy mode
WAI due to
MC-58297MC-58297describes the "opposite". It says that Minecraft calculates the block count in this example with 3*3*3 (which is not the case in the latest version, in hollow mode it is always 26 (instead of 27))Fixed in some 1.13 snapshot. Partial dupe of
MC-55800, but both issues are fixed.