Normal pickblock should give you the flower and Ctrl + Pickblock should give you the flower pot (+NBT)
Code analysis by @unknown can be found in this comment.
Linked issues
is duplicated by 1
Comments 12
Is this still a concern in the current Minecraft version 1.8.1 Prerelease 3 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Workaruond for placing flowerpots with a specific flower in them is using:
/give @p minecraft:flower_pot 1 0 {BlockEntityTag:{Item:"minecraft:red_flower",Data:0}}
only problem with that, it has a rendering/block loading bug.
1: You use the command above.
2: You place down the pot with the predetermined flower inside.
3: You need to re-open the world or press F3+A to reload the chunks and it will reload the pot and render it correctly.
(will also correctly render after placing any block in the world, after you place the pot.)
But it does work, after F3+A the correct flower/item is in the pot.
Please link to this comment in the description
The following is based on decompiled version of Minecraft 1.8 using MCP. All method and class names are the names used in the decompiled version.
The reason why this happens is that the private void middleClickMouse() method of the net.minecraft.client.Minecraft class has a special exception for flower pots. This should however only use the item in the flower pot if the flower pot contains one and CTRL is not pressed.
The following is my personal opinion:
The whole method and the public Item getItem(World worldIn, BlockPos pos) method of the net.minecraft.block.BlockFlowerPot class need therefor a rewrite as the item stored in the flower pot should be directly copied from the flower pot to the hotbar. Therefor the item inside a flower pot should be properly stored (see MC-91005).
Is this still an issue in the latest snapshot 16w44a? If so please update the affected versions.
This is an automated comment on any open or reopened issue with out-of-date affected versions.
Is this still a concern in the current Minecraft version 14w11b / Launcher version 1.3.11 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.