#Anti crash mod 1.12.2 mods#

Scroll down until you find the file forge.cfg.

Navigate to your server files and click the config folder.

To enable the error fixing Forge setting for Minecraft 1.12.2 and older, please follow these steps:

Once the problem has been fixed, we recommend changing the settings back to false to prevent any issues with your world.

When you next connect to your server and load the chunk with the ticking block entity, Forge will attempt to automatically remove the block which is causing issues. When your server starts, the new settings will take effect.

Then simply save the file and restart your server.

Change both of the settings from false to true as shown below.

Scroll down until you find the settings removeErroringEntities and removeErroringTileEntities which we've highlighted below.

Find the file forge-server.toml and click Edit.

Within your world folder, click the folder called serverconfig.

In this example, my world is called my-forge-world.

Navigate to your server files and click your world folder.To enable the error fixing Forge setting for 1.13 and newer, please follow these steps:

If you're running Minecraft 1.12.2 or older, please scroll further down the page to find more information. In Minecraft 1.13, Forge changed the location of the config file required to fix this issue. There's a slightly different way of fixing this error depending on which version of Forge you're running. Then once fixed, disable the setting and restart your server.Д«efore changing any settings, we highly recommend creating a backup of your world. We recommend enable the setting as a one off just to fix the problem. The setting is disabled by default because it can cause some funky things to happen to your world. You may of not known but Forge has a setting which allows you to automatically remove entities which are erroring. Now we've confirmed that the issue is a ticking block entity, we can go ahead and fix it. We've highlighted the line Description: Ticking block entity. Don't be put off by all the complex info! We've got an example server with the ticking block entity issue below. You can check to see if this is the issue by navigating to your server files, then click the crash-reports folder and view your most recent crash report. To put it simply, a ticking entity is either a modded block, mob or animal which will cause your server to crash.

#Anti crash mod 1.12.2 mods#

Here is a list of the (2) mods I have used before it crashed:ДЄll mods are for the 1.12.2 version and I have even updated forge to see if that would work, it is still crashing.Д¬rash-_17.06.32-client.If your Forge Minecraft Server is crashing whenever you connect, it's likely you have a ticking block entity. I have the very last crash report from 5.06PM today (it is now 5.17PM QLD). (I don't use Optifine usually)Д®verything works fine without any mods, however as soon as I place on in the mods folder, it crashes almost instantly. Drag it up one folder into the root of the game folder. For example, ThermalExpansion-3.0.0.b10a.jar. I tried it with Optifine to see if that would help but that wasn't much better. Login to your server FTP and navigate to the folder of the affected game. I have tried uninstalling Minecraft itself, tried uninstalling forge and reinstalling them all but it all still crashes. I have tried going through and seeing if it would work with any SINGLE mods but still it crashed every single time. I have tried a process of elimination, taking out the mods, restarting and putting them back. This morning the launcher crashes just before it takes me to the actual game window. Up untilВ yesterday around 1AM I was able to play with all mods perfectly fine.