Jump to content

Tick lag in 1.12.2 modded forge server, can't find cause


Recommended Posts

Hi! I've been struggling for a while with a bad problem on my 1.12.2 server, and after not finding any answer anywhere, and everything i tried having failed, i decided to post here and ask for help!


So a while ago i decided to try and make a 1.12.2 minecraft server (I have always previously played in 1.7.10) I dowloaded all the mods i had for my older server but for the newer version (plus a few extra ones), installed the recommended forge for 1.12.2, set up the server and all... But then I ran into a problem, the server gets a huge tick lag, causing the mobs to move weirdly and skip around and hits to not register properly, in the server console, I get messages like this "[Server thread/WARN] [minecraft/MinecraftServer]: Can't keep up! Did the system time change, or is the server overloaded? Running 2377ms behind, skipping 47 tick(s)" I am not sure, but I think this happens only when there is at least one player inside the server, not when the server is empty, but i could be wrong in this.


My pc specs are: Processor Intel core i5-4570 3.20GHz Graphic Card Nvidia GeForce GTX 1060 6GB and RAM 24GB


I am running the server with the forge version forge-1.12.2- which is the recommended one for 1.12.2 and the mods I am using are:

Ancient Warfare

Auto Reg Lib

Biomes O' Plenty

Classic Combat

Code Chicken Lib

Davincis Vessels

Deconstruction Table

DrZhark's Mo' Creatures

Flan's Mod

Mr.Crayfish Furniture

Hammer Core

IChun Util



Multi Mine

No More Recipe Conflict

Ore Lib

Pam's HarvestCraft



Rex's Additional Structures


Subterranean Waters

Twilight Forest


Things I have tried:

-Deleting all mods: Issue still appears, but it's almost unnoticeable, mobs just skip a little bit... I don't want to play without mods though! D:

-Allocating more RAM: I tried allocating 10GB, the server only used 2%-ish according to console and the problem persisted

-Lagoggles to find the issue: There seems to be nothing in my world causing lag according to Laggoggles

-Creating a brand new world: Same issue in freshly generated worlds

-Reducing render distance: I don't think I should be doing this with my specs... But it still fixes nothing...

I may have done something else and forgotten... I feel like I have tried anything but it just won't work!

EDIT: I have also tried reinstalling Java, I have the latest version and reinstalling did nothing to fix my issue


The weirdest thing of all is that my computer doesn't seem to be straining, and also my older 1.7.10 server with almost the same mods ran perfectly fine!

Can anyone help me with this?

Link to comment
Share on other sites

Post your log.

Some tips:


Modder Support:


1. Do not follow tutorials on YouTube, especially TechnoVision (previously called Loremaster) and HarryTalks, due to their promotion of bad practice and usage of outdated code.

2. Always post your code.

3. Never copy and paste code. You won't learn anything from doing that.



Programming via Eclipse's hotfixes will get you nowhere

5. Learn to use your IDE, especially the debugger.



The "picture that's worth 1000 words" only works if there's an obvious problem or a freehand red circle around it.

Support & Bug Reports:


1. Read the EAQ before asking for help. Remember to provide the appropriate log(s).

2. Versions below 1.11 are no longer supported due to their age. Update to a modern version of Minecraft to receive support.



Link to comment
Share on other sites

Post your log as described in my signature and the EAQ

About Me


My Discord - Cadiboo#8887

My WebsiteCadiboo.github.io

My ModsCadiboo.github.io/projects

My TutorialsCadiboo.github.io/tutorials

Versions below 1.14.4 are no longer supported on this forum. Use the latest version to receive support.

When asking support remember to include all relevant log files (logs are found in .minecraft/logs/), code if applicable and screenshots if possible.

Only download mods from trusted sites like CurseForge (minecraft.curseforge.com). A list of bad sites can be found here, with more information available at stopmodreposts.org

Edit your own signature at www.minecraftforge.net/forum/settings/signature/ (Make sure to check its compatibility with the Dark Theme)

Link to comment
Share on other sites

  • 11 months later...

Don't necropost.

1.12.2 isn't supported anymore, please update and make your own thread to receive support.

This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy.


As the most common issue I feel I should put this outside the main bulk:

The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge.

If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan.


For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety.


Logs (Most issues require logs to diagnose):


Please post logs using one of the following sites (Thank you Lumber Wizard for the list):

https://gist.github.com/100MB Requires member (Free)

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://hastebin.com/: 400KB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.


What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...


...for Installer Issues:

Post your installer log, found in the same place you ran the installer

This log will be called either installer.log or named the same as the installer but with .log on the end

Note for Windows users:

Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension


Where to get it:

Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs.


Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it).
  4. Now launch the pack through that profile and follow the "Mojang Launcher" instructions above.






or alternately, 


Fallback ("No logs are generated"):

If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft


Server Not Starting:


If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output.


Reporting Illegal/Inappropriate Adfocus Ads:


Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad.

Lex will need the Ad ID contained in that URL to report it to Adfocus' support team.


Posting your mod as a GitHub Repo:


When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.

When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.


  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. git remote add origin [Your Repository's URL]
      • In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. Navigate to GitHub and you should now see most of the files.
    • note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]


Link to comment
Share on other sites

This topic is now closed to further replies.


  • Create New...

Important Information

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