Jump to content

Modded Minecraft Server, Keeps lagging and thereby crashing


jimkerman

Recommended Posts

Hello, me and my friends have been playing a modded Minecraft server together and everything has been fine, however, all of the sudden out of nowhere the server keeps on crashing, I am not sure why. It does not matter where we are or what we are doing. We are running on 1.12.2 with the Latest version of forge for that version, I have attached here a crash report log file. Thank you all in advance for any help received! 

Crash Report https://www.dropbox.com/scl/fo/1m7dqw6yuq4xr6x8wx568/AEu414y1iQ5Pg5_qr8MAYl4?rlkey=6j0qpsax234mxgbsgxxw9oiyx&st=upc5d8xi&dl=0 

Link to comment
Share on other sites

Alright, well before removing IC2 I changed the max chunks from 15 to 6, and that seems to have fixed most of it, BUT, the console log keeps spamming out this "[16:01:09] [File IO Thread/WARN] [FML]: Large Chunk Detected: (11, 19) Size: 578 ./servermodworld2024oct/region/r.5.2.mca", and it is still lagging a little. What exactly does this mean and by some chance is this a chunk I can find and fix? If so how can I find it? After testing the server without IC2, the same error message still shows up, and the server continues to suffer in terms of lag.

Edited by jimkerman
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.