[MC-159508] Ctrl + Pick block on beehives and nests does not copy their honey levels

The bug

Bee nests and hives are copied with a outdated honey levels, when ctrl-pick-block is used.

To reproduce

Switch into Creative mode
Place an empty bee nest or hive
Adjust the honey level with a debug-stick, or wait for a bee to raise the level
Press Ctrl + Pick Block
Place the new bee nest/hive somewhere else
→ ❌ The newly placed bee nest/hive is not full of honey

Alternatively, breaking a nest in creative will generate a placeable copy of the nest with the correct honey value, but placing that nest and ctrl+picking it again, will always generate a nest with that new honey value, even if the level changes between placing and ctrl+picking.

Related issues

is duplicated by

MC-160219 Bee Nest/Hive NBT Data Problem

MC-276108 Ctrl+pick don't get honey levels

relates to

MC-48453 The pick block function used on filled chiseled bookshelves, lit furnaces, lit blast furnaces, and lit smokers doesn't copy their textures

MC-87296 Ctrl + Pick on Command block block does not save the conditional state

MC-159358 Beehive loses honey level when being broken without silk touch

MC-167906 Beehive items at full honey level do not appear with honey in inventory/as item/in hand

Attachments

MC-159508.mp4

Comments

migrated 2019-08-23T06:08:58Z

[media][media][media]

Cultist_O 2019-08-23T06:10:28Z

May relate to MC-141934 and/or MC-159383

violine1101 2019-08-23T11:17:41Z

This is related to block states, not NBT. I'm not sure whether Ctrl + Pick Block is supposed to copy the block state at all.

migrated 2019-08-31T21:43:13Z

same problem

tryashtar 2019-09-04T14:45:05Z

Doesn't seem fixed to me in 19w36a

migrated 2019-09-07T09:16:46Z

Can confirm that it's still an issue in 19w36a.
It only works when you punch the block in creative. The level will still be kept, even at the max level.

migrated 2019-11-12T16:16:29Z

Is it really an issue? The honey level is a block state and ctrl+pick block only copies NBT data.

supeika 2020-05-29T23:51:30Z

This bug would be invalid, because you could modify the block state with a debug stick.

But also this bug would be valid, because honey levels are affected on normal gameplay, so their values would be retained by Ctrl-Pick command.

Conclussion: This is Mojang staff decision. They would choose the best option.

Avoma 2021-02-03T19:26:42Z

Can confirm in 21w05a.

Avoma 2021-02-05T09:36:42Z

Can confirm in 21w05b.

Avoma 2021-02-17T19:14:04Z

Can confirm in 21w07a.

Avoma 2021-02-25T16:20:38Z

Can confirm in 21w08b.

Avoma 2021-07-22T12:10:05Z

Can confirm in 1.17.1.

Avoma 2021-12-20T14:37:27Z

Can confirm in 1.18.1.

Avoma 2022-03-07T14:40:47Z

Can confirm in 1.18.2.

Avoma 2022-08-10T18:19:32Z

Can confirm in 1.19.2.

migrated 2024-06-13T21:23:44Z

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.

Cultist_O 2024-06-13T23:17:35Z

Using a debug-stick to change the honey level seems to have the same effect as set-block, that is: Setting a hive to full with a debug stick, will create a honey block that will behave differently when ctrl-clicked than if it were first broken and replaced.

I cannot be sure when the behaviour changed, as I had been using a sticked hive for testing.

Edit: This doesn't quite seem to be quite complete. If the block is adjusted by a debug stick, or indeed by a bee, then ctrl+pickblock will behave as though the adjustment never happened. The only case where it preserves the honey level is if the block was broken and replaced in the way you suggest.

I will update the report