MC-127644Waterlogged blocks in structures spread to other waterloggable blocks when loading the structure
The bug
When loading a structure containing a waterlogged block, that waterlogged block will spread its waterlogged state to other waterloggable blocks next to or below it. This repeats for those newly waterlogged blocks.
How to reproduce
- Download the attached waterlogged_test.zip
datapack and install it - Place a structure block in the world
- Load the structure test:waterlogged_test
- All waterloggable blocks are waterlogged, even though in the waterlogged_test.nbt file in the data pack only one block has waterlogged=true.
Example
Here is an example in video: https://youtu.be/s_VxTfJxtuw
Linked Issues
Attachments1
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
Created Issue:
Waterlogged Blocks in Saved Structures
I found a bug where if you save and load any waterlogged blocks of any kind in a structure block, they will spread their waterlogged state to blocks that can be waterlogged (but previously weren't before) if they are in direct contact with the original waterlogged block (or any created on the loading of the structure).
Here's a video I made explaining the issue further: https://www.youtube.com/watch?v=s_VxTfJxtuw
Environment
This shouldn't matter.
This shouldn't matter.
The bug
When loading a structure containing a waterlogged block, that waterlogged block will spread its waterlogged state to other waterloggable blocks next to or below it. This repeats for those newly waterlogged blocks.
Here is a video showcasing the bug in detail.
To reproduce
- Download the attached waterlogged_test.zip
- Place a structure block in the world
- Load the structure test:waterlogged_test
- All waterloggable blocks are waterlogged, even though in the waterlogged_test.nbt file in the data pack only one block has waterlogged=true.
Original description
I found a bug where if you save and load any waterlogged blocks of any kind in a structure block, they will spread their waterlogged state to blocks that can be waterlogged (but previously weren't before) if they are in direct contact with the original waterlogged block (or any created on the loading of the structure).
Here's a video I made explaining the issue further: https://www.youtube.com/watch?v=s_VxTfJxtuw
WaterloggedBlocks inSavedStructuresWaterlogged blocks in saved structures spread their waterlogged state to other blocks when loading the structure
testing discovered
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
is duplicated by
![[Mod] Asteraoth](../../../data/avatars/users/92886.png){kind=small}
relates to
is duplicated by
is duplicated by
relates to
relates to
relates to
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
is duplicated by
The bug
When loading a structure containing a waterlogged block, that waterlogged block will spread its waterlogged state to other waterloggable blocks next to or below it. This repeats for those newly waterlogged blocks.Here is a video showcasing the bug in detail.
To reproduce
- Download the attached waterlogged_test.zip
- Place a structure block in the world
- Load the structure test:waterlogged_test
- All waterloggable blocks are waterlogged, even though in the waterlogged_test.nbt file in the data pack only one block has waterlogged=true.
Original description
I found a bug where if you save and load any waterlogged blocks of any kind in a structure block, they will spread their waterlogged state to blocks that can be waterlogged (but previously weren't before) if they are in direct contact with the original waterlogged block (or any created on the loading of the structure).
Here's a video I made explaining the issue further: https://www.youtube.com/watch?v=s_VxTfJxtuw
The bug
Infinite upward elytra flight is possible due to a potential oversight with water and not resetting upward velocity at world height.
This bug affects Minecraft Java Edition versions 1.13pre9 through 1.14.4.
To reproduce
- Place at least one water source at the max world height and add some blocks adjacent to it.
- Submerge yourself in said water; it doesn't need to be two blocks deep, you could just put your lower half in it.
The bug
Infinite upward elytra flight is possible due to a potential oversight with water and not resetting upward velocity at world height.
This bug affects Minecraft Java Edition versions 1.13pre9 through 1.14.4.
To reproduce
- Place at least one water source at the max world height and add some blocks adjacent to it.
- Submerge yourself in said water; it doesn't need to be two blocks deep, you could just put your lower half in it.
The bug
Infinite upward elytra flight is possible due to a potential oversight with water and not resetting upward velocity at world height.This bug affects Minecraft Java Edition versions 1.13pre9 through 1.14.4.
To reproduce
- Place at least one water source at the max world height and add some blocks adjacent to it.
- Submerge yourself in said water; it doesn't need to be two blocks deep, you could just put your lower half in it.
The bug
When loading a structure containing a waterlogged block, that waterlogged block will spread its waterlogged state to other waterloggable blocks next to or below it. This repeats for those newly waterlogged blocks.
Here is a video showcasing the bug in detail.
To reproduce
- Download the attached waterlogged_test.zip
- Place a structure block in the world
- Load the structure test:waterlogged_test
- All waterloggable blocks are waterlogged, even though in the waterlogged_test.nbt file in the data pack only one block has waterlogged=true.
Original description
I found a bug where if you save and load any waterlogged blocks of any kind in a structure block, they will spread their waterlogged state to blocks that can be waterlogged (but previously weren't before) if they are in direct contact with the original waterlogged block (or any created on the loading of the structure).
Here's a video I made explaining the issue further: https://www.youtube.com/watch?v=s_VxTfJxtuw
Waterloggedblocks insaved structuresspread theirwaterlogged state to other blockswhenloading thestructureWaterlogged Blocks in Structures Spread to Other Waterloggable Blocks When Loading the Structure
WaterloggedBlocks inStructuresSpread toOtherWaterloggableBlocksWhenLoading theStructureWaterlogged blocks in structures spread to other waterloggable blocks when loading the structure
is duplicated by
Confirmed in 1.16 prerelease 8. - Specifically - structure containing a waterlogged block will cause all non-waterlogged blocks to become waterlogged upon loading.
![[Helper] ZeNico13](../../../data/avatars/users/31913.png){kind=small}
The bug
When loading a structure containing a waterlogged block, that waterlogged block will spread its waterlogged state to other waterloggable blocks next to or below it. This repeats for those newly waterlogged blocks.
Here is a video showcasing the bug in detail.
To reproduce
- Download the attached waterlogged_test.zip
- Place a structure block in the world
- Load the structure test:waterlogged_test
- All waterloggable blocks are waterlogged, even though in the waterlogged_test.nbt file in the data pack only one block has waterlogged=true.
Original description
I found a bug where if you save and load any waterlogged blocks of any kind in a structure block, they will spread their waterlogged state to blocks that can be waterlogged (but previously weren't before) if they are in direct contact with the original waterlogged block (or any created on the loading of the structure).
Here
's a video I made explaining the issue further: https://www.youtube.com/watch?v=s_VxTfJxtuwThe bug
When loading a structure containing a waterlogged block, that waterlogged block will spread its waterlogged state to other waterloggable blocks next to or below it. This repeats for those newly waterlogged blocks.
How to reproduce
- Download the attached waterlogged_test.zip
- Place a structure block in the world
- Load the structure test:waterlogged_test
- All waterloggable blocks are waterlogged, even though in the waterlogged_test.nbt file in the data pack only one block has waterlogged=true.
Example
Here is an example in video: https://youtu.be/s_VxTfJxtuw
is duplicated by
is duplicated by
![[Mod] Jarl-Penguin](../../../data/avatars/users/92849.png){kind=small}
![[Mod] SPGoding](../../../data/avatars/users/44622.png){kind=small}
is duplicated by
![[Helper] Johnibur](../../../data/avatars/users/28381.png){kind=small}
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
duplicates
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
testing discovered
is duplicated by
relates to
Does this happen if you replace the fences with solid blocks?
If it doesn't, this might be MC-127644.
Alright. Then the flowing water blocks are just converting because the waterlogged fences create infinite water sources. Resolved as a duplicate of MC-127644.
Thank you for your report!
We're actually already tracking this issue in MC-127644, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MC-127644, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
However, we are already tracking this issue, and this report is a Duplicate of MC-127644, which is a report that has not been resolved yet.
If you want, you can upvote the parent ticket, and enable watching to receive any updates about it - if you believe you have any information that may be important for this issue, please leave a comment on the parent. Please also use the search function in the future to prevent duplicate reports.
Quick Links:
📓 Issue Guidelines – 🛠 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
💬 Mojira Subreddit – 💬 Mojira Discord
Thank you for your report!
We're tracking this issue in MC-127644, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
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:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Confirmed. This issue does not occur while saving, but when loading the structure.
I attached a data pack that adds a structure test:waterlogged_test in which only the slab is waterlogged. When loading the structure, all waterloggeable blocks will be waterlogged.
I cannot confirm that settings in structure blocks don't get saved, this works perfectly fine for me. If you continue having issues with that, please consider making a new report about that (if you don't find another report about this).
(PS: I edited your report a little, I hope you're fine with that)
Yes, perfect. Do you know if this has been fixed?
Confirmed for 18w31a
Still present in 18w43b.
Duplicate of
MC-130584They're not completely the same – the tickets have different ways to reproduce.
Can confirm that this bug is still in 1.14.3 Pre 1
Somehow I was able to make a structure where this glitch didn't occur but I can't seem to reproduce it
This is still an issue in 1.14.4.
It does only occur when blocks are actually copied in. If the waterloggable blocks are already in place (non-waterlogged) the water doesn't spread.
Unbelievable this still exists. I was the first to report this 2 years and 4 months ago, with many duplicates since then. This is a big bug! Come on Mojang!
There are way more important bugs that need to be fixed. Complaining here will do nothing and is just annoying. If you don't have to add anything to add to the ticket, please don't comment.
confirmed in pre 2
Confirmed in 1.15 full release
Confirmed in 1.16 Snapshot 20w06a.
In 20w29a