This only happens on 1.16.100. Randomly when traveling in and out of the nether one of my double chests will appear as a singular chest. There will be an outline of the full chest but when you try to open the chest it usually crashes the game. Also when you click on the singular part of the chest it only shows the top slots of the double chest but when you click on the unrendered part it shows all the slots. The only solution I have found is to destroy and replace the chest. The world was created in the previous version.
World download linkprovided in this comment.
Linked issues
is duplicated by 42
relates to 2
Attachments
Comments 63

Does this occur in vanilla Minecraft, without any resource packs?
The ticket will automatically reopen when you reply.
Does this occur in vanilla Minecraft, without any resource packs?
The ticket will automatically reopen when you reply.
@Caleb Johnson: If the chests were affected before the 1.16.201 Hotfix then they probably won’t fix themselves. You will likely need to break and replace them, and then they should not glitch again.
So we've had this issue occur with a storage system on a 1.16.200 private server. With a mix of chests crossing the chunk boundary variously broken and not broken, handy.
The actual cause of this issue is that the double chests are (somehow) losing their pairing coordinates, TBH I'd be curious if the cause is tangentially linked to the villagers on chunk boundaries dissappearing issue.
Anyway, depending on the chest it looks like they either completely lose the pairing coordinates or they're reset to 0,0. The side that loses their pairing coordinates remains functional as a single chest. The side that references 0,0... crashes the server. For my amusement, I placed a chest at 0,0 at the same Y height and... it still crashed. I'm guessing because that chest didn't have the required backreference pairing coordinates to the other chest.
[media]
[media]
Once 1.16.201 is live, we'll break and replace the chests and report back on if the issue reoccurs or not.
EDIT: Apparently 1.16.201 has been live since mid-December.... our hoster hasn't released the update for the server yet, yay....
BTW this is what a working double chest looks like, well, half of one.
[media]So we've had this issue occur with a storage system on a 1.16.200 private server. With a mix of chests crossing the chunk boundary variously broken and not broken, handy.
The actual cause of this issue is that the double chests are (somehow) losing their pairing coordinates, TBH I'd be curious if the cause is tangentially linked to the villagers on chunk boundaries dissappearing issue.
Anyway, depending on the chest it looks like they either completely lose the pairing coordinates or they're reset to 0,0. The side that loses their pairing coordinates remains functional as a single chest. The side that references 0,0... crashes the server. For my amusement, I placed a chest at 0,0 at the same Y height and... it still crashed. I'm guessing because that chest didn't have the required backreference pairing coordinates to the other chest.
[media]
[media]
Once 1.16.201 is live, we'll break and replace the chests and report back on if the issue reoccurs or not.
EDIT: Apparently 1.16.201 has been live since mid-December.... our hoster hasn't released the update for the server yet, yay....
BTW this is what a working double chest looks like, well, half of one.
[media]@Azarel Out of curiosity, what would happen if you added the doublechest tags for the chest you placed at 0,0?