I believe marking this as Working as Intended is not a great decision. Using text formatting codes allows us to make things unique. As an add-on creator, I use it in the description of an add-on to emphasize certain information. Without this, I lose a vital piece of communication with add-on users.
Affects 1.21.92
This affects Preview 1.21.100.20
This is not an issue in the latest Preview version, 1.21.90.27. I’m not sure which version it was originally fixed in.
After further testing, I have discovered a possible workaround for this specific use case.
Typing in "/place structure httyd:dragon_hunter_ship ~ 63 ~ true" (true means ignore start_height) will place the structure at a specific location. Being able to set a specific xyz value in the jigsaw file, instead of a start_height and heightmap_projection, could open up the ability for floating structures that are based on coordinates, not world generation.
Steps to Reproduce:
Attach mcpack to a Minecraft Preview world with Data-Driven Jigsaw Structures enabled.
Locate structure ( /locate structure httyd:dragon_hunter_ship )
Notice structure is nearly always on the ocean floor
Observed Results:
The structure is on the highest solid block.
Expected Results:
The structure should be on the highest non-air block, which is water.
I just attached the add-on to the files.
Yes. This is resolved.
Due to OP’s inactivity, I created an example behavior pack. It works in 1.21.100 with no experiments enabled. I would also be willing to take over control of this report if that is deemed reasonable.
When I interact with this tamed wolf, I receive an error saying that the property “tamedToPlayer” is undefined. I have it set up to send a chat message when I have interacted, and the result of
[media][media]tamedToPlayer
,tamedToPlayerId
, andisTamed
The script file is below, in addition to the behavior pack.