Possible NBT tag too big on 1.20.1 Forge modded server. How to find source?

On my Forge 1.20.1 (~100 mods) server, whenever I approach and load my base, about 25% of the time, I get disconnected with the error:
Internal Exception: io.netty.handler.codec.DecoderException: java.lang.RuntimeException: Tried to read NBT tag that was too big; tried to alloate: 2097176bytes where max allowed: 2097152
Internal Exception: io.netty.handler.codec.DecoderException: java.lang.RuntimeException: Tried to read NBT tag that was too big; tried to alloate: 2097176bytes where max allowed: 2097152
Attempting to log in again usually works, since it just rolls the dice again on whether or not a too-big NBT tag gets loaded. I've narrowed it down to a few chunks that are potentially problematic, but none of these chunks, to my knowledge, have especially complex entities that would store too much NBT data. I ran minecraft-nbt-depth-checker but it didn't detect any problematic NBT tags. Deepest depth was only 11. I'm also confused why it's only SOMETIMES that the NBT tag size is a problem, but the majority of times I load my base, it's fine. I also can't easily restore from a backup, because there wasn't a defined point in time where the problem started happening. It started as an extremely rare occurence but slowly become a little more common over the course of a few weeks. So, my tl;dr questions: 1) How can I find the byte sizes of the NBT tags of the chunks in my base? 2) What would cause the inconsistent tag size behavior, where sometimes when I load in, I get disconnected due to NBT size, and other times it's totally fine? 3) Is it safe to just install a mod like XL Packets, or better to figure out the underlying cause instead? (Assuming the cause isn't just that I have a lot of mods that have a lot of NBT data, enough to go over the 2MB limit)
No description
0 Replies
No replies yetBe the first to reply to this messageJoin

Did you find this page helpful?