Hello Users!
So, I've been seeing a lot of these crashes recently and I do know what the issue is and there is a fix!
There is an Easter Egg in IC2 and unfortunately it is not working with the other mods in certain modpacks. Direwolf20/YogPack/Unleashed are the most common ones!
To fix this issue you will need to do TWO things in your server.properties file:
1. Spawn monsters sets to "false"
2. Difficulty set to "0"
This will set your server to not spawn any mobs/hostile mobs which is causing the ticket entity error. You will need to have this set for the next 48 hours until Halloween passes.
Even though this crash is not related to Railcraft, this can fix your issues as well:
You can turn off Season Module from Railcraft from the modules.cfg in the config folder. Works both for server and client.
Another alternative is to set your date/time on your computer/machine to something that isn't halloween - that is not very optimal for servers, so please use option 1.
This is the stack trace provided from the error/crash. If you do not have a crash/error report and you are still crashing, try this fix any way.
So, I've been seeing a lot of these crashes recently and I do know what the issue is and there is a fix!
There is an Easter Egg in IC2 and unfortunately it is not working with the other mods in certain modpacks. Direwolf20/YogPack/Unleashed are the most common ones!
To fix this issue you will need to do TWO things in your server.properties file:
1. Spawn monsters sets to "false"
2. Difficulty set to "0"
This will set your server to not spawn any mobs/hostile mobs which is causing the ticket entity error. You will need to have this set for the next 48 hours until Halloween passes.
Even though this crash is not related to Railcraft, this can fix your issues as well:
You can turn off Season Module from Railcraft from the modules.cfg in the config folder. Works both for server and client.
Another alternative is to set your date/time on your computer/machine to something that isn't halloween - that is not very optimal for servers, so please use option 1.
This is the stack trace provided from the error/crash. If you do not have a crash/error report and you are still crashing, try this fix any way.
- ---- Minecraft Crash Report ----
- // Why is it breaking
- Time: 10/30/13 2:09 PM
- Description: Exception ticking world
- java.lang.RuntimeException: java.lang.NullPointerException
- at ic2.core.IC2.onLivingSpecialSpawn(IC2.java:2270)
- at net.minecraftforge.event.ASMEventHandler_29_IC2_onLivingSpecialSpawn_LivingSpecialSpawnEvent.invoke(.dynamic)
- at net.minecraftforge.event.ASMEventHandler.invoke(ASMEventHandler.java:35)
- at net.minecraftforge.event.EventBus.post(EventBus.java:103)
- at net.minecraftforge.event.ForgeEventFactory.doSpecialSpawn(ForgeEventFactory.java:52)
- at yp.a(SpawnerAnimals.java:245)
- at yp.a(SpawnerAnimals.java:187)
- at in.b(WorldServer.java:162)
- at net.minecraft.server.MinecraftServer.r(MinecraftServer.java:669)
- at ho.r(DedicatedServer.java:269)
- at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:599)
- at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:497)
- at fy.run(SourceFile:849)
- Caused by: java.lang.NullPointerException
- at ic2.core.IC2.onLivingSpecialSpawn(IC2.java:2268)
- ... 12 more