Another Damn Ticking Memory Connection Error - Crashes When I load World

[STAT1S]

I'm trying to find the mod.crash-2020-04-19_07.36.15-server.txt

[DavidM]

FnafAddon is made with MCreator and is broken. You should delete it.

 

Oh and 1.12 is no longer supported on these forums. Please update to a modern version of Minecraft to receive support.

Edited April 19, 2020 by DavidM

[STAT1S]

DAVIDM, I found the mod It was Railcraft.

 

I made FNAFAddon, and it is not the problem. May I ask what is wrong with mcreator as I have seen a lot of hate.

[DavidM]

3 hours ago, STAT1S said:

DAVIDM, I found the mod It was Railcraft.

 

I made FNAFAddon, and it is not the problem. May I ask what is wrong with mcreator as I have seen a lot of hate.

Please read the log. FNAFAddon is the problem.

Railcraft just happened to trigger the broken part of FNAFAddon, and removing it might solve the problem temporarily, but the crash will happen again as soon as another mod access the same thing. You can try removing your mod instead of Railcraft, and the crash would no longer persist.

Railcraft is trying to access the block state from a stack (which is normal and will be done by many mods), however MCreator screwed up the block state on the block, effectively causing the crash due to not initializing properly.

 

MCreator creates problematic code that 1) has terrible performance 2) cause random crashes due to bad initializations (I.e. static initializations with registry objects) 3) does not have proper sided code and therefore will crash on server 4) cluster up the mod jar with unnecessary code 5) bad coding style. It also claims to be the owner of whatever the user creates according to the license.

 

If you want to make a mod, please learn Java and make a real mod.

Edited April 19, 2020 by DavidM