Background:
1) when a water source block is placed, it will flow around in a radius. however, a waterloggable block prevents water from flowing into itself.
2) 2 water source blocks separated by a single block flow together to form a water source block at the location.
Bug: When two water source blocks are separated by a waterloggable block, a new source block will still be created inside of the waterloggable block, even though water isnt supposed to be able to get inside of the waterloggable block from the outside.
Recreating the bug (illustrated with provided image)
1) dig two 3x1 trenches. inside one of them, place any waterloggable block in the middle, for example a fence.
expected outcome: nothing happens.
real outcome: expectation is confirmed.
2) place water in one of the corners in both trenches.
expected outcome: water spreads across the entire trench with no waterloggable block in the middle, but in the other trench, the waterloggable block prevents the water from flowing further.
real outcome: expectation is confirmed.
3) place water in the other corner in both trenches.
expected outcome: in the trench with no waterloggable block, two water sources flowing freely create a third water source in the middle of the trench. in the other trench, the waterloggable block in the middle of the trench prevents two water sources from meeting, thus nothing will happen.
real outcome: expectation about the first trench is confirmed. however, the waterloggable block didnt prevent two water sources from meeting and a source block was created inside of the waterloggable block.
Linked issues
Attachments
Comments 3
aha its indeed similar, upon seeing it and related issues i agree that this is duplicate. but how is it works as intended? makes zero sense.
Thank you for your report!
We're tracking this issue in MC-130203, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as working as intended, which means this is not considered a bug and won't be fixed. Please do not leave a comment on the linked ticket.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
-- I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
This seems really similar to MC-130203, which was resolved as "Works As Intended".