mojira.dev
MC-12842

Items with unsupported data values stack on certain events such as item pickup and shift-click

For instance, say I give myself one emerald and place it in a chest.
/give VergilPrime 388 1
then I give myself another emerald with an ID of 1
/give VergilPrime 388 1 1
If I shift click the 388:1 into the chest, or the 388 into my inventory, they will become either a stack of two 388 or a stack of 2 388:1.
If have both in my inventory and throw one on the ground, then pick it back up, it will stack with the other and lose its data as well.

Comments 9

For instance, say I give myself one emerald and place it in a chest.
/give VergilPrime 388 1
then I give myself another emerald with an ID of 1
/give VergilPrime 388 1 1
If I shift click the 388:1 into the chest, or the 388 into my inventory, they will become either a stack of two 388 or a stack of 2 388:1.

If have both in my inventory and throw one on the ground, then pick it back up, it will stack with the other and lose its data as well.

Unable to reproduce. Giving myself 388 1 1 gives me the default emerald.

http://youtu.be/nZyp5YEmM88 <<< This should make it more clear.
The problem doesn't occur when using the give command, the items stack over eachother when:
A. You have 388 in your inventory, then pick up 388:1 off the ground, or
B. You have 388 in your inventory, and shift click 388:1 out of a chest.
or vice-versa.

Problem is still present in Minecraft 1.7.2

You do realize that data values will be going away and no longer able to be used? I suggest you learn to use the new format minecraft:asset as when data values are disabled it will invalidate this ticket. I'm tempted to close it now, but it's still relevant for the time being.

Yes I know, and it's unfortunate this never got fixed while it was relevant. I suppose resource packs, display names and lore can all be used to the same effect though.

Is this still a concern in the current Minecraft version 14w07a / Launcher version 1.3.9 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.

Is this still a concern in the current Minecraft version 1.7.9 / 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.

This ticket is incomplete without the requested information, no response has been received within a reasonable time and we are assuming the issue has been resolved. If you are still experiencing this issue, we can reopen it at your request.

Please review the guidelines before reporting issues.

Dustin A Mundy

(Unassigned)

Unconfirmed

Minecraft 1.5.1, Minecraft 1.7.2

Retrieved