Suso
- Suso
- suso
- Europe/Stockholm
- Yes
- No
MC-147750
When trying to edit the contents of a chest and selecting a specific slot iside of Items[
{}], on top of editing that slot, the contents of Items[0] will be removed.Recreating the issue:
- Place a chest and fill its first three slots with items.
- Run /data modify block [x] [y] [z] Items[1] set value {anything_works_here:2711}
As you can see, this would delete the contents of slot 2 as expected, but ends up removing slot 1 in the process as well. Any other slots work properly as illustrated by slot 3.
When trying to edit the contents of a chest and selecting a specific slot iside of Items[], on top of editing that slot, the contents of Items[0] will be removed.
Recreating the issue:
- Place a chest and fill its first three slots with items.
- Run /data modify block [x] [y] [z] Items[1] set value {anything_works_here:2711}
As you can see, this would delete the contents of slot 2 as expected, but ends up removing slot 1 in the process as well. Any other slots work properly as illustrated by slot 3.
When trying to edit the contents of a chest and selecting a specific slot iside of Items[], on top of editing that slot, the contents of Items[0] will be removed.
Recreating the issue:
- Place a chest and fill its first three slots with items.
- Run /data modify block [x] [y] [z] Items[1] set value {anything_works_here:2711}
As you can see, this would delete the contents of slot 2 as expected, but ends up removing slot 1 in the process as well. Any other slots work properly as illustrated by slot 3.
When trying to edit the contents of a chest and selecting a specific slot iside of Items[], on top of editing that slot, the contents of Items[0] will be removed.
Recreating the issue:
- Place a chest and fill its first three slots with items.
- Run /data modify block [x] [y] [z] Items[1] set value {anything_works_here:2711}
As you can see, this would delete the contents of slot 2 as expected, but ends up removing slot 1 in the process as well. Any other slots work properly as illustrated by slot 3.
When trying to edit the contents of a chest and selecting a specific slot iside of Items[], on top of editing that slot, the contents of Items[0] will be removed.
Recreating the issue:
- Place a chest and fill its first three slots with items.
- Run
/data modify block [x] [y] [z] Items[1] set value {anything_works_here:2711}As you can see, this would delete the contents of slot 2 as expected, but ends up removing slot 1 in the process as well. Any other slots work properly as illustrated by slot 3.
When trying to edit the contents of a chest and selecting a specific slot iside of Items[], on top of editing that slot, the contents of Items[0] will be removed.
Recreating the issue:
- Place a chest and fill its first three slots with items.
- Run
/data modify block [x] [y] [z] Items[1] set value {anything_works_here:2711}As you can see, this would delete the contents of slot 2 as expected, but ends up removing slot 1 in the process as well. Any other slots work properly as illustrated by slot 3.
When trying to edit the contents of a chest and selecting a specific slot iside of Items[], on top of editing that slot, the contents of Items[0] will be removed.
Recreating the issue:
- Place a chest and fill its first three slots with items.
- Run
/data modify block [x] [y] [z] Items[1] set value {anything_works_here:2711}As you can see, this would delete the contents of slot 2 as expected, but ends up removing slot 1 in the process as well. Any other slots work properly as illustrated by slot 3.
When trying to edit the contents of a chest and selecting a specific slot iside of Items[], on top of editing that slot, the contents of Items[0] will be removed.
As explained by
Recreating the issue:
- Place a chest and fill its first three slots with items.
- Run
/data modify block [x] [y] [z] Items[1] set value {anything_works_here:2711}As you can see, this would delete the contents of slot 2 as expected, but ends up removing slot 1 in the process as well. Any other slots work properly as illustrated by slot 3.
When trying to edit the contents of a chest and selecting a specific slot iside of Items[], on top of editing that slot, the contents of Items[0] will be removed.
As explained by
Recreating the issue:
- Place a chest and fill its first three slots with items.
- Run
/data modify block [x] [y] [z] Items[1] set value {anything_works_here:2711}As you can see, this would delete the contents of slot 2 as expected, but ends up removing slot 1 in the process as well. Any other slots work properly as illustrated by slot 3.
When trying to edit the contents of a chest and selecting a specific slot iside of Items[], on top of editing that slot, the contents of Items[0] will be removed.
As explained by Franco Caprile in the comments, the issue seems to be caused by the Slot tag being copied, overriding the index used to select what slot to put the info into.
Recreating the issue:
- Place a chest and fill its first three slots with items.
- Run
/data modify block [x] [y] [z] Items[1] set value {anything_works_here:2711}As you can see, this would delete the contents of slot 2 as expected, but ends up removing slot 1 in the process as well. Any other slots work properly as illustrated by slot 3.
Seems to crash when a player goes under the world limit (Y=0) here. The world crashes permanently, even if the player that caused this to trigger is no longer there.
crash-2018-07-16_21.16.29-server.txt
EDIT: Maybe the game is trying to spawn mobs on subchunk -1?
Just tested it on 18w30b, still broken for me
@Franco Caprile After checking, this seems to be what's causing the issue. Still, I don't thin this should be considered intended behaviour, since you're specifying a position in the array, I think the slot tag shouldn't be copied. It makes sense because the slot is stored inside of the item in the array, but I don't find it useful in any case. If you're trying to copy an item from a slot in a chest to another one, it would be much more convenient if the Slot tag adjusted automatically, since that would allow to use the "searching by tag" (Items[\{tag:{}}]) much more versatile.
I'll update the description of the issue with hat we found out.
Hi! I'm running into a similar issue that's better described by other reports such as
MCL-21838, but that have been marked as duplicate of this one. The issue has persisted for over a week now and makes it impossible to start neither java nor bedrock edition from the launcher.@Donuts1000 Logging out and back into the microsoft store did the trick. Thanks!