Steps to Reproduce:
Get a void world or get empty some chunks using fill command or travel to the End
Put some water(or lava but water faster) using fill or setblock command.
Let water flow until world border(y=-64).
Remove water source or close around.
Observed Results:
Some of flowing waters never runs out.
If you remove remaining flowing waters by commands or placing block by hand or using sponge they comes back when chunk reloaded.
If you put another block instead of this bugged water block, same error repeats for that block.
Expected Results:
Water flows until it runs out.
Edit: Here is a video. Water cannot be removed(v1). If I try to put another block and remove them, the bug is inherited to the new block(v2).
Linked issues
is duplicated by
Attachments
Comments


I deleted some worlds where I saw this problem. The two worlds I have at the moment are those prepared for the marketplace and that I cannot share due to the NDA. But as I said it's not a world specific problem, all you need is an empty chunk, minus height and some water.

Is there a language related problem because I use translation? Because I'm saying it's not a problem that happens at certain coordinates in a particular world. This problem is happening on "all" worlds. When I say "all" I mean "each instance of its kind", so it's a "general" bug that happens on "every" seed in "all" worlds you'll create in Bedrock version 1.18 or later of Minecraft. It happens at minus/negative coordinates.
For the use of the fill command, you can use the wiki. Rest assured it will work. For the command to work, you don't need a special number value, a secret magic word that you can only hear from me.
I was thinking that this problem could only be on my computer but a few hours after I created this issue I saw another similiar issue. That person was having the same issue with the another blocks(i think it was gold blocks).
Sorry, but I couldn't find it when I searched the issue again.
If you are wondering about the description of water or how to download minecraft feel free to ask. I would be happy to provide more detailed information.

Can you please provide a video showcasing the issue?
This ticket will automatically reopen when you reply.

[UPDATE]: 11/08/2023
Oh. I have my example world. => My issue: MCPE-165724
= Version Bugs [CONFIRMED] =
Can to comfirn at 1.19.80.22 - Preview
Can to comfirn at 1.19.80.23 - Preview
Can to confirm at 1.19.73
Can to confirm at 1.20.0.21 - Preview
Can to confirm at 1.20.0.22 - Preview
Can to confirm at 1.19.81 - Hotflix
Can to confirm at 1.20.0
Can to confirm at 1.20.30.21 - Preview [NEW]

https://youtu.be/oQgImtsflZc here is an reproduction.

An attachment with a disallowed file extension has been removed from this ticket.
Executable files and documents are not allowed as attachments.
Please attach crash reports, log files and screenshots as they are instead of pasting them into a document.
-- I am a bot. This action was performed automatically! If you think it was incorrect, please notify us on Discord or Reddit

(sorry in advance, I'm French I use Google translate)
I started writing to share my findings after playing with the bug and finally I feel like I have an interesting lead. I don't know anything about programming or how the game works, so maybe I'm totally wrong. However, my tests with the bug may perhaps help to resolve it, I hope so in any case.
All blocks placed between layer 0 and layer 16 are likely to bug.
So maybe layer 16 is misconfigured and is actually layer 0 or at least has the property of being one, which makes it theoretically impossible to place blocks under this layer.
BUT ! Basically, the creative player cannot go below layer 0. It is as if he were on impassable ground.
The fact that layer 16 is considered layer zero allows the player to be in a zone below zero and which prohibits the laying of blocks when located below it.
So to summarize, the zone from layer 0 to 16 is probably poorly configured, because it is considered to be below 0 from 16, i.e. an impossible zone for laying blocks.
This would justify the fact that I manage to delete blocks by placing an “allow” block layer because these blocks force the zone to adopt a state which authorizes destruction but that I cannot destroy the allow blocks themselves .
I hope the translation was not bad.

I can confirm for 1.21.2
It happens in the overworld, nether and end, if that helps.
This makes for a really easy and powerful duplication glitch in survival, since you can place blocks on an empty chunk in the end, break them and pick them up, reload the world, and the blocks will be back but you'll still have the items in your inventory, resulting in your blocks being duplicated.

Can confirm for 1.20.70, 1.20.71, 1.20.72, 1.20.80, 1.20.81, 1.21.0, 1.21.1 and 1.21.2. Happens to me in the End dimension on Realms on Nintendo Switch and IOS

I can confirm for 1.21.44 on Windows 😞
Can you upload an example world for repro?