Steps to reproduce:
1) Give yourself a bundle with items inside such that the fullness exceeds 64. In the example videos, I used
/give @s bundle{Items:[{id:"minecraft:bow",Count:2b}]}
/give @s bundle{Items:[{id:"minecraft:stone",Count:65b}]}
/give @s bundle{Items:[{id:"minecraft:stone",Count:66b}]}2) Grab an item in your inventory and right-click the overfilled bundle with it
3) The item should remain being dragged by your cursor, but its Count will be increased by the bundle's (fullness−64), and the bundle will have an "air" item with Count (64−fullness) in it
Bundle's NBT Before:
{Items: [{id: "minecraft:stone", Count: 66b}]}Bundle's NBT After:
{Items: [{id: "minecraft:air", Count: -2b}, {id: "minecraft:stone", Count: 66b}]}Attachments
Comments 4
Also, this is not caused by 1 item having a stack count of over 64. Not just that, multiple items with a valid stack size also cause this bug to happen. The size only needs to exceed 64.
Found that while I was testing my Bigger Bundles datapack. It has been bugging me for so long.
Again, this proves my theory of Mojang not fixing ANY bugs if they don't affect vanilla gameplay. You guys can go and raid people's bug reports with this theory. Pretty sure we can find out which resolution goes to which bug now ourselves.
oh nooooooo why won't they fix this?
https://www.youtube.com/watch?v=-bPu7halXyA&start=27
I guess they don't like custom bundles ... I personally loved this project.