So instead, we'll have to take the long road. I had this idea first of moving items to the chest first and manipulating the slot numbers so they're fixed, but no, items with invalid IDs or invalid slot numbers are immediately deleted, leaving no time to manipulate the slot numbers. Use the other coordinates of the double chest to get the others. Simply: /item block 12 23 34 container.0 copy entity hotbar.0Īnd there you go! Remember, chest slots only go up to 27. Now, it'll only take one command per slot, instead of three, and we don't need to create such a big setup. This lets us copy item slots with ease, rather than having to worry about having invalid slot numbers. Say hello to /item, taking such burdens off of our bodged workarounds. So what can you do to solve this problem? The other half is still stored in the chest you didn't break. This is why, when you break a double chest filled to the brim with items, only half its items drop. This applies to how the items are stored, half the chest using up slots 0–27 of one of the two sides of the block, and the other half using slots 0–27 of the other side. Although it looks like one block entity, it is really two chests joined together. When you try to set them, they are automatically deleted by the system.īut what about a double chest? Shouldn't it have double the number of slots, 0–53?Ī double chest takes up the width of two blocks.
These share slot numbers with your inventory hotbar and the top two rows, so no wonder they are copied there! The third row, with slot numbers 27–35, is not copied, because their slot numbers are higher than the allowed slots in a chest. So, with your command, the item in inventory slot 0 (first hotbar) goes to chest slot 0, inventory slot 1 to chest slot 1, and so on.Ī single chest uses slot numbers from 0–26, numbered in reading order starting with 0 in the top left.
The only reason your old command works is because the chest shares slot numbers with your inventory's hotbar and top two rows.
0 kommentar(er)
