If you are in a world on a server, placing or removing a block over the void causes a decoder exception to be thrown, kicking all members that have the area loaded client-side. If there is a block somewhere in the 1x256x1 block column regardless of where it is, the error does not happen. It only happens when a block is placed (in a completely empty column) or broken (causing the entire column to be empty).
Error is shown here. This is from the client. There are no error messages in the console.
[media]Linked issues
is duplicated by 5
Attachments
Comments 8
I have added a little more context to this. Error message from the client, and a screenshot from console showing where the errors happened (red lines)
I am unable to reproduce this bug. I tried in singleplayer, LAN and dedicated server, worlds created before and after 20w45a. Could you provide steps to reproduce? Perhaps share a world where this is happening.
This comment on MC-203911 claims that only tinted glass is affected, even though MC-204040 claims that bedrock is affected.
The world was a flatworld created on 20w45a. I know for a fact it affects at least dirt and bedrock. It seems like it is every block which is placed in an empty column, or a block which is broken to make a column empty.
1_locks a lot when I enter.
2 when there are updates or when I enter worlds with TLMODS the skin is deleted.
3_and this is the last complaint, that when I mongo the map mod does not let me open it or remove the death point.1_locks a lot when I enter.
2 when there are updates or when I enter worlds with TLMODS the skin is deleted.
3_and this is the last complaint, that when I mongo the map mod does not let me open it or remove the death point.
From what I know this works with any full block (I've tried it on purpur, bedrock, obsidian) and for the server I play on there is an issue where the 1.17 snapshot clients disconnect but using something like fabric with ViaFabric installed allows me to connect with a 1.16 client and does not show the message which means it might be a client problem but its fabric with a mod so its still not known if its the 1.17 client but it is a high likelihood. Another thing is the glitch has a "temper" only working sometimes and at certain Y levels so I'd say do a full void world and try for about 10 minutes placing and breaking stuff at really anywhere
Note: This occurs at random places for the world I play on
Please provide the full error message and server log.