MC-272105Decorated Pot is missing the "contents" implicit data component type
The minecraft:decorated_pot item type is missing the minecraft:container data component from it's "implicit" data components. This causes the pick block functionality to be inconsistent for decorated pots. Placing down a plain decorated pot with /give @s decorated_pot and then using (regular) middle-click to pick it back up and inspecting the two, we see
Original: {count: 1, id: "minecraft:decorated_pot"}
Picked: {components: {"minecraft:container": []}, count: 1, id: "minecraft:decorated_pot"}
This is because the decorated_pot definition in Items.java doesn't have a default component value registered for the container data component type. Every other block entity that has a "container" has a default value set for the container component type which means that after picking the block for those, the 2 components are equal and it isn't included in the data component patch for the stack.
LowCreated Issue:
Decorated Pot is missing the "contents" implicit data component type
The minecraft:decorated_pot item type is missing the minecraft:container data component from it's "implicit" data components. This causes the pick block functionality to be inconsistent for decorated pots. Placing down a plain decorated pot with /give @s decorated_pot and then using (regular) middle-click to pick it back up and inspecting the two, we see
{"minecraft:container": []}
Original: {count: 1, id: "minecraft:decorated_pot"}
Picked:{{{components:, count: 1, id: "minecraft:decorated_pot"}}}
This is because the decorated_pot definition in Items.java doesn't have a default component value registered for the container data component type. Every other block entity that has a "container" has a default value set for the container component type which means that after picking the block for those, the 2 components are equal and it isn't included in the data component patch for the stack.
The minecraft:decorated_pot item type is missing the minecraft:container data component from it's "implicit" data components. This causes the pick block functionality to be inconsistent for decorated pots. Placing down a plain decorated pot with /give @s decorated_pot and then using (regular) middle-click to pick it back up and inspecting the two, we see
{"minecraft:container": []}
Original: {count: 1, id: "minecraft:decorated_pot"}
Picked:{{{components:, count: 1, id: "minecraft:decorated_pot"}}}
This is because the decorated_pot definition in Items.java doesn't have a default component value registered for the container data component type. Every other block entity that has a "container" has a default value set for the container component type which means that after picking the block for those, the 2 components are equal and it isn't included in the data component patch for the stack.
The minecraft:decorated_pot item type is missing the minecraft:container data component from it's "implicit" data components. This causes the pick block functionality to be inconsistent for decorated pots. Placing down a plain decorated pot with /give @s decorated_pot and then using (regular) middle-click to pick it back up and inspecting the two, we see
Original: {count: 1, id: "minecraft:decorated_pot"}
Picked:{components: {"minecraft:container": []}, count: 1, id: "minecraft:decorated_pot"}This is because the decorated_pot definition in Items.java doesn't have a default component value registered for the container data component type. Every other block entity that has a "container" has a default value set for the container component type which means that after picking the block for those, the 2 components are equal and it isn't included in the data component patch for the stack.
The minecraft:decorated_pot item type is missing the minecraft:container data component from it's "implicit" data components. This causes the pick block functionality to be inconsistent for decorated pots. Placing down a plain decorated pot with /give @s decorated_pot and then using (regular) middle-click to pick it back up and inspecting the two, we see
Original: {count: 1, id: "minecraft:decorated_pot"}
Picked: {components: {"minecraft:container": []}, count: 1, id: "minecraft:decorated_pot"}This is because the decorated_pot definition in Items.java doesn't have a default component value registered for the container data component type. Every other block entity that has a "container" has a default value set for the container component type which means that after picking the block for those, the 2 components are equal and it isn't included in the data component patch for the stack.
![[Mod] Greymagic27](../../../data/avatars/users/92875.png){kind=small}
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
![[Mojang] Triage Team](../../../data/avatars/users/89842.png){kind=small}
![[Mod] turbo](../../../data/avatars/users/92867.png){kind=small}
![[Mod] Nassim Jahnke](../../../data/avatars/users/94205.png){kind=small}
is duplicated by
![[Bot] Piston](../../../data/avatars/users/31202.png){kind=small}
![[Mod] Jiingy](../../../data/avatars/users/91802.png){kind=small}
Thank you for your report!
We're tracking this issue in MC-272105, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
I can confirm that after picking up a placed down pot, it has 1 more componant. However, please provide the command(s) needed to inspect the item to confirm the rest of this report.
You can just use /data get entity @s SelectedItem to view the data component structure serialized to NBT while holding each item and see the difference
Thanks