You may have exceeded the maximum size of a chunk's compressed NBT in vanilla but that's unlikely. The key difference is NBTExplorer s full support for Minecraft. NBTExplorer is a low-level graphical NBT data editor originally based on NBTedit. It supports reading and writing in a number of formats including Standard NBT files (e.g. Decompress the chunks and look for any that exceed 2,097,152 bytes when decompressed. NBTExplorer is an open source graphical NBT (Named Binary Tag) data editor for Minecraft. You may have a chunk with a lot of stuff in it that's pushing these boundaries. A typical newly-generated chunk in 1.13 vanilla will save everything in a few clusters. Look for chunks that appear to have a lot of data (a high value for the length byte). The chunk data for each chunk is saved in contiguous 4096-byte blocks that are the same size as a disk cluster. These 32-bit integers encode a one-byte length followed by an address offset. The Anvil format has a header of 1024 32-bit integers followed by the chunk data. You should be able to do this if you have access to an NBT library that recognises the Anvil format. I would scan all the chunks with a low-level NBT parser. The chunk may need a little TLC to bring it down to below this hard limit. It is possible that the chunk has saved correctly but the game is not allowing it to decompress because it's exceeding this limit. The error message is suggesting there's a hard limit somewhere that is 2,097,152 bytes (this is 512 × 4096). Uncompressed NBT data will be higher than this because NBT compresses well. I can provide more information if I need to, I just figured this would be the best to start with.Ī vanilla chunk in Anvil format cannot store more than 255 × 4096 = 1,044,480 bytes of compressed NBT data unless something is done to increase this limit. The more I search, the seedier things get as well, and I'm just at the point where I figured I'd ask here. ![]() Another is NBT Exploits by storing filled chests inside chests inside chests, but also nothing. Most things we find pertaining to this issue have to do with custom inventories, so we tried removing mods that have those, but nothing. We don't, however, have any issues with loading things in Single Player, it's ONLY in multiplayer does this issue happen. We've tried removing mods one by one and loading the world, but the issue persists, leading me to believe that it's vanilla. The server is modded, Minecraft, 1.12.2, using the following mods: We've been trying for months now to try to fix this issue, and we've tried rolling back, deleting chests, and so on. A server I play on is having a massive issue, as one of our more often visited areas are causing crashes on the server. ![]() The number of the attempted allocation varies, but the rest is static.Īfter a few months of looking and finding no answers, I've decided to ask here. This is the error message we get when we get booted.
0 Comments
Leave a Reply. |