Tried to read NBT tag that was too big
See original GitHub issueA 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?
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Tried to read NBT tag that was too big - Java Edition Support
I have a problem on my Minecraft 1.12.2 modded server, the server is running fine I play with my friend (2 players in...
Read more >Tried to read NBT tag that was too big error. - Minehut Forums
I'd suggest you try restarting your server to fix this issue. If this doesn't work, you could try removing this (see image) including...
Read more >Tried to read NBT tag that was too big · Issue #742 - GitHub
The chunk that causes the crash has a block with too much NBT data. This is usually caused by a bunch of apotheosis...
Read more >Tried to read NBT tag that was too big; tried to allocate - Reddit
The server owner should check the server log for the exact location of the event that caused the player to be kicked then...
Read more >"Tried to read NBT tag that was too big" kick loop after mining ...
How to recreate: 1. Use something like NBT Explorer or the the "/more" command on a paper server with essentials installed to create...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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