mojira.dev
MC-58812

Pick-Block and drag will only create a limited number of stacks for an item

I was trying to fill up a chest with eggs (in creative mode) so I could test a system where items would get put in the first available chest, but then I found a problem...

What I expected to happen was...:
I expected to be able to hold the pick-block key with an egg, and fill up the whole chest in one drag of the mouse

What actually happened was...:
However, it would not copy more slots than you originally had items in the stack.

Steps to Reproduce:
1. place a chest
2. grab an egg from the creative inventory
3. open the chest
4. middle-click on egg
5. middle-click and drag in the chest's inventory, trying to fill the chest

Linked issues

Comments 8

Christopher Teal

I think I have a theory on why this is the case: Since this functionality is related to the functionality of splitting a stack by left-click (or right-click) dragging, I think that there is a restriction that in the other cases would prevent splitting the stack so far that it can't cover the slots requested. Since a full stack of eggs is 16, it's trying to say it can't split any farther, even though it's not actually splitting the stack (it's copying them.). Basically: this is a carry-over restriction that ought not to apply to this specific feature. I hope what I said makes enough sense to be useful.

Christopher Teal

I've now tested a 64-stackable item in a 'triple-chest' (shameful I know, using a bug for investigating another bug), and I've noticed that it tries to copy only 64 stacks, and won't go any farther. It looks like my theory is holding so far.

Christopher Teal

Update: I've actually noticed that if you start with a smaller stack, it will only let you create as many full stacks as items you had in your original stack. EDIT: just to make it clear, for this, you just take the stack and middle-click-drag it into the inventory

Does this still affect the current version/snapshot 1.8.1/1.8.2-pre1?

Christopher Teal

It still affects 1.8.2-pre1

Confirmed for 1.9.4.

Confirmed in 1.10.1

1.10.1 is a bit under 3 years old, and isn't supported anymore. And this bug was fixed in 16w43a, which is a snapshot for 1.11. 1.10.1 was definitely affected at the time, but you should update if you want fixes.

Christopher Teal

(Unassigned)

Confirmed

Minecraft 14w25b, Minecraft 14w26c, Minecraft 14w28b, Minecraft 14w32a, Minecraft 1.8-pre1, ..., Minecraft 16w33a, Minecraft 16w39b, Minecraft 16w41a, Minecraft 16w42a, Minecraft 16w43a

Minecraft 16w44a

Retrieved