1.14.4 armor_stand not loading at all when loaded "procedurally", marker or no. By "precedurally" means as in an armor_stand placed within an nbt file of a default structure, which loads as the terrain is procedurally generated. This was specifically discovered when attempting to place an armor_stand statue in the entrance.nbt of the woodland_mansion structure directory. Marker or not, the armor_stand does will not load.
Attachments
Comments 7
I understand the setting on the structure_block's .nbt file includeEntities may default to the off setting, but that should set to yes if the user saves the .nbt file as such, no?
Well entities can be ignored both when saving and loading, unfortunately we don't have control over the loading part for vanilla structures.
For what it's worth, I discovered a work-around to load custom entities (armor_stand statue in this case) into a mansion by taking advantage of a falling entity, a pressure plate, and a couple chained command blocks.
[media]
See attached datapack, with a custom minecraft:structures/woodland_mansion/entrance.nbt wherein an armor_stand entity is posed at the entrance to serve as a statue.
You'll see entities do not load procedurally... in that worldgen-created woodland mansions will not have the entity. The custom polished_stone pillar on which the entity should be placed will be present, evidence that the custom structure nbt is properly replacing vanilla default entrance during worldgen.
To see the expected entity, use a structure block to manually load the minecraft:structures/woodland_mansion/entrance.nbt
[media]
The woodland mansion structure is explicitly loaded with
ignoreEntitiesset to true. This is almost definitely intended