We are trying to load 1.2.5 to play a Vech's map. I keep getting this error. I reloaded 1.8.x and switched to default resource pack.
Any assistance would be appreciated.
Generated 8/2/15 2:54 PM
Minecraft: Minecraft 1.2.5
OS: Windows 7 (amd64) version 6.1
Java: 1.8.0_45, Oracle Corporation
VM: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
LWJGL: 2.9.0
OpenGL: GeForce GTX 960/PCIe/SSE2 version 4.5.0 NVIDIA 353.30, NVIDIA Corporation
java.lang.ArrayIndexOutOfBoundsException: 2
at iz.a(SourceFile:256)
at if.a(SourceFile:254)
at mw.a(SourceFile:192)
at lr.b(SourceFile:734)
at net.minecraft.client.Minecraft.x(SourceFile:752)
at net.minecraft.client.Minecraft.run(SourceFile:671)
at java.lang.Thread.run(Unknown Source)
--- END ERROR REPORT 52aefa01 ----------
Okay- it seems this is a pretty common error/crash. I deleted the options file. Crash. I created a new 1.2.5 directory and pointed the profile to that directory. Crash.
We are trying to load 1.2.5 to play a Vech's map. I keep getting this error. I reloaded 1.8.x and switched to default resource pack.
Any assistance would be appreciated.
Generated 8/2/15 2:54 PM
Minecraft: Minecraft 1.2.5
OS: Windows 7 (amd64) version 6.1
Java: 1.8.0_45, Oracle Corporation
VM: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
LWJGL: 2.9.0
OpenGL: GeForce GTX 960/PCIe/SSE2 version 4.5.0 NVIDIA 353.30, NVIDIA Corporation
java.lang.ArrayIndexOutOfBoundsException: 2
at iz.a(SourceFile:256)
at if.a(SourceFile:254)
at mw.a(SourceFile:192)
at lr.b(SourceFile:734)
at net.minecraft.client.Minecraft.x(SourceFile:752)
at net.minecraft.client.Minecraft.run(SourceFile:671)
at java.lang.Thread.run(Unknown Source)
--- END ERROR REPORT 52aefa01 ----------
Okay- it seems this is a pretty common error/crash. I deleted the options file. Crash. I created a new 1.2.5 directory and pointed the profile to that directory. Crash.
I'm stuck.
Is that the whole crash report? It seems rather... short.
It is what comes up on the screen after it crashes, yes.
However. I just loaded the map in 1.3.2 (or whatever) and it seems to work fine. So I got a work-around.