Tried to read NBT tag that was too bigSee original GitHub issue
A player of ours keeps having issues when they put ME drives into a travler’s sack. They get the following error.
[16:47:16] [Netty Client IO #1/ERROR] [FML]: NetworkDispatcher exception io.netty.handler.codec.DecoderException: java.lang.RuntimeException: Tried to read NBT tag that was too big; tried to allocate: 2097227bytes where max allowed: 2097152
Is there something you can do on your end to resolve this or should I report this to the author of Applied Energistics?
- Created 5 years ago
- Comments:6 (1 by maintainers)
Top GitHub Comments
Contrary to what everyone is saying, this is actually an issue with Actually Additions. The sack’s specific item contents should not be synced to the client via NBT, but rather just when the container gets opened (which happens automatically). This would avoid large tags exceeding the packet limit. Check the Storage Crate code for reference, as its ItemBlock does this exact thing.
Closed via ac2bc01