Bowswa
Assigned
No issues.
Reported
Comments
can partially confirm in 1.21 full release.
The behavior seems to now only apply to full honey blocked placed with /setblock, potentially other force place methods(i did not test those)
However once i BROKE the block in creative, dropping the item, and then placed and picked, it did correctly copy and place with the data. My guess is some behavior has been fixed by item components, as picking after that process would properly copy the component, but force placement NOT using components cannot be picked.
i can reproduce this issue
To add to the latest comment, since this "Working as Intended" resolution, it has taken me an additional 3-20 seconds to move structures from the "generated" folder to the datapack they were made for. Bear in mind that i work with a datapack that currently has a dozen different namespaces(for organization of code), and dozens more are in my plans. Each namespace i have to add 3 additional clicks, and a bigger selection than i would for just copying the namespaces themselves with the updated structures.
While this may have indeed been working as intended, it has, as i and Dhranios pointed out, caused a further issue that an alternate solution to MC-272347 would alleviate.