[SPIGOT-5251] Large Chunk Detected Created: 07/Aug/19  Updated: 09/Aug/19  Resolved: 07/Aug/19

Status: Resolved
Project: Spigot
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: edmon cruz Assignee: Unassigned
Resolution: Invalid Votes: 0
Labels: bug, crash, error, spigot, world
Environment:


Windows 10 64 Bit - Java 8 - 4GB of RAM


Version: 1.14.4
Guidelines Read: Yes

 Description   

[01:19:26] [Server thread/WARN]: Large Chunk Detected: ([-26, 0]) Size: 377 .\ogworld\region\r.-1.0.mca

I get this error on my server every so often. I'm not sure what's the cause of it. Server runs fine but when i go to the specified chunk my client starts to act weird. In this chunk i'm able to place blocks or throw items. At a certain point my client disconnects me from the server. I am unable to successfully log in with out getting booted out again. A quick fix i've been doing is deleting the chunk file but i loose any progress on the chunk if it was somewhere i have been building in. Is there a way to increase the chunk size limit or any other fix that doesn't make my server loose a lot of progress?



 Comments   
Comment by edmon cruz [ 09/Aug/19 ]

I have linked the chunk file below since the file is to big to be attached here.

https://drive.google.com/open?id=11i5ZmCU_HiCYB2PJgScxrvnOisOJRnmp

Comment by md_5 [ 08/Aug/19 ]

Well you could upload the problematic chunk

 

It's almost certainly not a bug, just people overloading the chunk with valid items

Comment by edmon cruz [ 08/Aug/19 ]

How would i check because now other players on the server are starting to be affected by it too.
They are telling me "at a certain point we start to lag till we can't do anything and eventually timed out"
My command line isn't saying any error messaged other than the Large Chunk being detected

Comment by md_5 [ 07/Aug/19 ]

>At a certain point my client disconnects me from the server.

 

Sounds like a client or unrelated issue, but more information is required.

The large chunk detected message is not itself an issue.

Generated at Tue Apr 15 09:10:39 UTC 2025 using Jira 10.3.3#10030003-sha1:d220e3fefc8dfc6d47f522d3b9a20c1455e12b7b.