-
Bug
-
Resolution: Unresolved
-
None
-
1.17.30.22 Beta, 1.17.30.21 Beta, 1.17.30.20 Beta, 1.17.11 Hotfix, 1.17.10, 1.17.20.20 Beta, 1.17.10.22 Beta, 1.16.220.51 Beta, 1.16.210.51 Beta, 1.16.50 Hotfix (iOS), 1.16.40 Hotfix, 1.16.100, 1.16.210, 1.17.0, 1.17.2 Hotfix, 1.20.71 Hotfix
-
None
-
Confirmed
-
Multiple
-
449146
The block(layer 0) will be moved.
But the water(layer 1) will be cloned(rather than moved) to the destination then(next tick) the residual water(layer 1) will become a new water block(layer 0).
Steps to reproduce:
- /setblock ~ ~ ~ water
- /setblock ~ ~ ~ seagrass
- /clone ~ ~ ~ ~ ~ ~ ~2 ~ ~ masked move
Observed Results:
- At ( ~+2, ~, ~), a waterlogged seagrass appears.
- At ( ~, ~, ~), the water remains and can't be removed in the same tick. "/testforblock ~~~ air" shows that ( ~, ~, ~) is air, which is visually not. It's just the waterlog hasn't become a normal water block.
- Next tick, ( ~, ~, ~) is a water block.
Expected Results:
( ~, ~, ~) should be completely empty after moving.
- clones
-
MCPE-46986 "/clone ⋯⋯ move" can't perfectly move waterlogged blocks
- Resolved
- relates to
-
MCPE-58121 /setblock air in a waterlogged block places water instead
- Open
-
MCPE-36301 /fill...replace fails to remove water from waterlogged blocks
- Reopened
-
MCPE-179847 /clone...filtered does not filter out water from waterlogged blocks, and will waterlog any block in target area
- Open
-
MCPE-153903 Bubble column cloned using the /clone command appears invisible
- Resolved