The bug
When loading a structure containing waterloggable blocks (which are not waterlogged) next to or inside a water source, the blocks inside the structure become waterlogged.
This is related to MC-130584, but not the same issue since MC-130584 is about water sources inside the structure spreading; while this report is about external water sources not being replaced and spreading inside the structure.
Note: In some cases this behavior might be desired, e.g. for shipwrecks. Maybe the structure file should support specifying whether a block removes water or becomes waterlogged onces loaded next to / inside water.
Linked issues
is duplicated by 7
MC-132868
Waterlogged fence in woodland mansion
Resolved
MC-133445
Custom structures are waterlogged
Resolved
MC-145151
Structure blocks don't remove water
Resolved
MC-170160
structure blocks dont reset waterlogged blocks
Resolved
MC-205350
Structure Block copy function with waterlogged blocks
Resolved
relates to 3
MC-250028
Waterloggable blocks within structures can generate waterlogged when next to chunk borders while other waterlogged blocks are present nearby
Open
MC-130584
When a structure loads, water sources in the structure spread into waterloggable blocks
Resolved
MC-169698
Blocks within igloo basements can generate waterlogged when generating in close proximity to water
Resolved
Attachments
Comments 11
Ideally structure blocks would have a setting to toggle this behavior, and this setting would be true for eg. shipwrecks and false for most other structures. This would also fix MC-169698.
It won't, only if the water was present before the loading, which is basically intended so structures can be spawned in water, and be submerged.
This is a major oversight if there really is no way of preventing it from happening. I created a structure with redstone in it, but there is one stair block that gets waterlogged, and the water wipes out all the redstone.
@Marcono1234 .... this ticket is closed as "works as intended", however something seems to be amiss - the problem is neither resolved, nor capable of being a valid game expectation?
From what I can tell, there are 2 possible scenarios here ...
INCORRECT BEHAVIOUR ❌
A structure is saved with a block that can be waterlogged, but that block is NOT waterlogged at save time (i.e. it is saved with the waterlogged block state as false) .... then during world generation, the structure is generated in water, and the block in question is in the middle of the structure, nowhere near other water source blocks. But because the structure was generated in water, the waterlogged block state of the respective block is now set to true.
Examples of this incorrect behaviour can be clearly seen in a valid and opened ticket here:
CORRECT BEHAVIOUR ✔
A structure is saved with a block that can be waterlogged, but that block is NOT waterlogged at save time (i.e. it is saved with the waterlogged block state as false) .... then during world generation, the structure is generated in water, and the block in question is in at the EDGE of the structure, between water source blocks. Thus, post-generation, the waterlogged block state becomes true, despite the save state being false. No problem with this behaviour.
Please can we get assistance on this ticket to determine it's validity and have it reopened. – Affects 1.19.3 ....
Seed: -9066070196958847497
Coords: /execute in minecraft:overworld run tp @s -13549.54 60.67 -8508.50 236.25 31.80
This mess up the redstone build. I use sign to block water, and after loading structure back in the water spread everywhere.
Reopened this report since MC-130584 has been changed to be only about water sources inside structures spreading.