Shulker in structure gets loaded where it got saved
When you save a structure with shulkers in it, the shulkers will appear at the position in the world were you saved the structure rather then were you loaded it.
The reason why this happens is because Shulkers have additionally to the Pos:[] -tag as well APX, APY and APZ which keep track of the Shulker's position in the world.
If you open the *.nbt-File with an external tool and remove these tags, it will work as expected.
For testing you can use shulkerTest.nbt in the attachments. It will spawn the Shulker always at 0, 70, 0.
Created Issue:
Shulker in structure gets loaded were it got saved
When you save a structure with shulkers in it, the shulkers will appear at the position in the world were you saved the structure rather then were you loaded it.
The reason why this happens is because Shulkers have additionally to the Pos:[] -tag as well APX, APY and APZ which keep track of the Shulker's position in the world.
If you open the *.nbt-File with an external tool and remove these tags, it will work as expected.
When you save a structure with shulkers in it, the shulkers will appear at the position in the world were you saved the structure rather then were you loaded it.
The reason why this happens is because Shulkers have additionally to the Pos:[] -tag as well APX, APY and APZ which keep track of the Shulker's position in the world.
If you open the *.nbt-File with an external tool and remove these tags, it will work as expected.
For testing you can use shulkerTest.nbt in the attachments. It will spawn the Shulker always at 0, 70, 0.
Shulker in structure gets loaded where it got saved
relates to
duplicates
Attached shulkerTest.nbt from my original ticket for shulkers (MC-102644). It's a structure file that will spawn a shulker at 0, 70, 0 but should spawn it above the structure block if the bug gets fixed.

I can also confirm this issue.
Still exists in MC version 1.10.
Relates to
MC-102170Why is this a duplicate of a bug report posted later than my original one?
Because my goal was to have it contain all situations in which it can cause problemsI first tried to add the information as comment to
MC-102170, a similar bug to this one, but noticed that doing that with comments will get a mess, so I created a new report which is supposed to contain all situations. I hope you are alright with thatAh I see, great work, I didn't really look at the ticket.
[Mod] NeunEinser, this report is already closed as duplicate and therefor there is no need to keep the affected version up to date.
I added 1.11.2 for MC-108149 instead