Robert Luman
Assigned
Reported
Comments
Guess I should pay better attention. Thanks for your help, guys!
Guess I should pay better attention. Thanks for your help, guys!
Adding the slot tag here does not fix the issue. When the slot tag is entered like this:
/setblock ~0 ~0 ~-2 minecraft:chest 0 destroy {Items:[{id:274,count:1,slot:1},{id:275,count:1,slot:2}]}The chest is still created with only the last item in the list, not both.
Adding the Slot tag as follows does not fix the issue.
/setblock ~0 ~0 ~-2 minecraft:chest 0 destroy {Items:[{id:274,count:1,slot:1}]}When the command is issued by the command block, the item doesn't just fall into the hopper, it no longer exists in any chest or hopper in the mechanism.
If I take out the second item definition, it works just fine. I've tried different variations on including a second item in the list and they all error. This was the only one I could get to not error. If someone has the correct way for defining additional items to go in the chest, please let me know.
Of course, it doesn't help that the description field is formatting the command weirdly for me. That should be on one line if it doesn't show up that way.
I get this same issue in single-player survival. I have a number of chests set up with an item frame on the end with an item showing what I have stored in the chest. In any snapshot after 13w37b, the chests and item frames do not render. I have the latest driver for my graphics card. I have a crash report if that will help.