This bug report is a parity issue with Java.
Summary:
In the bedrock version, the big dripleaf allows water to pass through, and in the Java version, the big dripleaf does not allow the flowing water.
Affect any height big dripleaf.
Steps to reproduce:
Place a water source.
Try to block the path with the flowing water with the help of big dripleaf.
Observed results:
The water will not react in any way to the big dripleaf.
Expected results:
Big dripleaf will block the path of the flowing water.
Image:
Java
[media][media]Bedrock
[media]Linked issues
Attachments
Comments 7
@unknown
Hello.
You described everything correctly, however this report is not about waterlogging and water behavior when placing incomplete blocks in flowing water. This report is about blockage of flowing water by big dripleaf. In bedrock, as in Java, almost all blocks that can become swamped can block flowing water (with the exception of small dripleaf which, when placing in flowing water on clay in Java, creates a source, and in the bedrock version does not create a source (and generally because of MCPE-139018 is placing even without clay), but this report, as I said above, is not at all about waterlogging).
Bedrock:
[media]Java
[media]This is not a bug, it is about water flowing mechanics. There are other blocks in Bedrock that work this way too, such as lever, repeaters and end rods. If anything it is a parity problem for Java since their water logging is a lot less of a complete feature, having some blocks that work like this is actually very useful. Anyways like what was already said this is not a bug since the difference is from before 1.15, and yes, not all blocks block flowing water on Bedrock.
@unknown: Developers themselves determine to correct oddness in java or in bedrock (as a rule, this happens most often in bedrock). In addition, there are blocks in the bedrock through which water does not flow, so this can be fixed without changing the mechanics!
I wasn't claiming it can't be fixed and would require changing mechanics or that it wasn't different than Java, just that it isn't nessecerilly a bug. As was said above parity differences from before 1.15 are not considered bugs and since Bedrock has many similar block to this it is not strange behavior for dripleaf to behave in this manner too.
The way waterlogging works between Bedrock & Java are completely different. In Java it needs a source block to be waterlogged in bedrock any water source can waterlog a block. Therefor there is no issue here. Also the parity issue wouldn't be valid since the issue here is waterlogging mechanics which was before the buzzy bees update