Here's the error report:
---- Minecraft Crash Report ----
// I bet Cylons wouldn't have this problem.
Time: 12/16/12 3:25 PM
Description: Exception in server tick loop
java.lang.IllegalArgumentException: Failed to register dimension for id 0, One is already registered
at net.minecraftforge.common.DimensionManager.registerDimension(DimensionManager.java:66)
at xcompwiz.mystcraft.MystcraftEventHandler.registerDimensions(MystcraftEventHandler.java:50)
at xcompwiz.mystcraft.MystcraftEventHandler.handleWorldLoadEvent(MystcraftEventHandler.java:37)
at net.minecraftforge.event.ASMEventHandler_58_MystcraftEventHandler_handleWorldLoadEvent_Load.invoke(.dynamic)
at net.minecraftforge.event.ASMEventHandler.invoke(ASMEventHandler.java:35)
at net.minecraftforge.event.EventBus.post(EventBus.java:103)
at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:278)
at hg.c(DedicatedServer.java:153)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:454)
at fp.run(SourceFile:818)
Relevant Details:
- Minecraft Version: 1.4.2
- Operating System: Windows 7 (amd64) version 6.1
- Java Version: 1.7.0_09, Oracle Corporation
- Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
- Memory: 489972744 bytes (467 MB) / 514523136 bytes (490 MB) up to 1908932608 bytes (1820 MB)
- JVM Flags: 2 total; -Xms512M -Xmx2G
- AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
- FML: ~ERROR~ NullPointerException: null
- Is Modded: Definitely; 'forge,fml'
- Profiler Position: N/A (disabled)
- Vec3 Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
- Player Count: 0 / 25; []
- World FTB-Beta-A Entities: 0 total; []
- World FTB-Beta-A Players: 0 total; []
- World FTB-Beta-A Chunk Stats: ServerChunkCache: 0 Drop: 0
- Type: Dedicated Server
I have no idea what's going on. The server was lagging badly so my friend and I decided that we should up the amount of ram. I closed the server and opened the 6GB Bat file, and this crash started happening. At first I thought it was just the 6GB file crashing, so I started using other ones, and they still gave the same result.
---- Minecraft Crash Report ----
// I bet Cylons wouldn't have this problem.
Time: 12/16/12 3:25 PM
Description: Exception in server tick loop
java.lang.IllegalArgumentException: Failed to register dimension for id 0, One is already registered
at net.minecraftforge.common.DimensionManager.registerDimension(DimensionManager.java:66)
at xcompwiz.mystcraft.MystcraftEventHandler.registerDimensions(MystcraftEventHandler.java:50)
at xcompwiz.mystcraft.MystcraftEventHandler.handleWorldLoadEvent(MystcraftEventHandler.java:37)
at net.minecraftforge.event.ASMEventHandler_58_MystcraftEventHandler_handleWorldLoadEvent_Load.invoke(.dynamic)
at net.minecraftforge.event.ASMEventHandler.invoke(ASMEventHandler.java:35)
at net.minecraftforge.event.EventBus.post(EventBus.java:103)
at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:278)
at hg.c(DedicatedServer.java:153)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:454)
at fp.run(SourceFile:818)
Relevant Details:
- Minecraft Version: 1.4.2
- Operating System: Windows 7 (amd64) version 6.1
- Java Version: 1.7.0_09, Oracle Corporation
- Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
- Memory: 489972744 bytes (467 MB) / 514523136 bytes (490 MB) up to 1908932608 bytes (1820 MB)
- JVM Flags: 2 total; -Xms512M -Xmx2G
- AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
- FML: ~ERROR~ NullPointerException: null
- Is Modded: Definitely; 'forge,fml'
- Profiler Position: N/A (disabled)
- Vec3 Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
- Player Count: 0 / 25; []
- World FTB-Beta-A Entities: 0 total; []
- World FTB-Beta-A Players: 0 total; []
- World FTB-Beta-A Chunk Stats: ServerChunkCache: 0 Drop: 0
- Type: Dedicated Server
I have no idea what's going on. The server was lagging badly so my friend and I decided that we should up the amount of ram. I closed the server and opened the 6GB Bat file, and this crash started happening. At first I thought it was just the 6GB file crashing, so I started using other ones, and they still gave the same result.