Summary:
If the light block waterlogged by flowing water is replaced by blocks waterlogged only in the source, the flowing water will not be removed, but will simply continue to exist with a "non-waterlogged" block.
With the rest of the blocks waterlogged in the flowing water (lever for example), this works with the /setblock command.
This does not seem to affect the gameplay in any way, but the fact that these blocks cannot be waterlogged simply by placing them in the flowing water indicates that this is not intentional.
Steps to reproduce 1:
Arrange the water so that flowing water forms.
Place the light block in the flowing water.
Replace the light block with a waterlogged block only in a full block of water (pointed dripstone or Amethyst for example).
Just place the same block in the flowing water as in the previous step.
Steps to reproduce 2:
Arrange the water so that flowing water forms.
Place waterlogged in flowing water block (lever for example).
Replace using the command /setblock the block with a block that does not waterlogged in flowing water (bell for example).
Just place the same block in the flowing water as in the previous step.
Observed results:
Blocks that do not become waterlogged in flowing water may become waterlogged because replacing blocks waterlogged in flowing water does not remove the flowing water.
Expected results:
Flowing water will be removed by replacing the blocks waterlogged in flowing water with blocks that do not waterlogged in flowing water.
Video:
[media][media]Image:
[media]Linked issues
Attachments
Comments 6
@unknown you are absolutely right. This works with the /setblock command, and therefore with blocks similar to the light block (which are swamped in flowing water). I have updated the report.
/setblock can be used to put blocks in all kinds of “illegal” positions, for example levers floating in air (MCPE-52857) or water in the nether. The reason why is that it skips the usual block checks and block updates that occur when placing a block. I’m not sure that’s a bug, since it is only possible with cheats and it could be convenient for map-making.
I sort of checked the problem for a duplicate and didn't find any similar reports. Also, what you voiced is (most likely) intentional (for example, the water in the nether MC-82137).
This can be a bug as it allows blocks to be placed in the flowing water that should block it, and doing this in a "rather strange way" could indicate unintended behavior. However, I do not argue that this can be useful and even very beautiful for map creators, for example, since it can allow such blocks as pointed dripstone and bell to be placed in the flowing water.
I agree, it's only possible with commands and it seem like it will allow some cool builds in Creative so I don't think it should be removed.
Does this only work when using the /setlbock command, or does it happen when breaking and replacing?