Game keeps crashing after getting banned

Discussion in 'General Help' started by FishFr0g, Jun 24, 2015.

Thread Status:
Not open for further replies.
  1. Offline

    FishFr0g

    Any help would be appreciated. I was banned from a server and now I get this everytime I start MC:

    ---- Minecraft Crash Report ----
    // Everything's going to plan. No, really, that was supposed to happen.

    Time: 6/24/15 11:16 PM
    Description: Initializing game

    java.lang.ExceptionInInitializerError
    at bxq.b(bxq.java:147)
    at bxq.b(bxq.java:125)
    at bxf.a(SourceFile:368)
    at bsu.a(SourceFile:809)
    at bsu.aj(SourceFile:465)
    at bsu.a(SourceFile:299)
    at net.minecraft.client.main.Main.main(SourceFile:120)
    Caused by: com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1
    at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:176)
    at com.google.gson.Gson.fromJson(Gson.java:803)
    at com.google.gson.Gson.fromJson(Gson.java:741)
    at The5zigModConfigManager.loadConfig(The5zigModConfigManager.java:105)
    at The5zigModConfigManager.setupWorkspace(The5zigModConfigManager.java:33)
    at The5zigModConfigManager.<init>(The5zigModConfigManager.java:22)
    at The5zigMod.<clinit>(The5zigMod.java:19)
    ... 7 more
    Caused by: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1
    at com.google.gson.stream.JsonReader.beginObject(JsonReader.java:374)
    at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:165)
    ... 13 more


    A detailed walkthrough of the error, its code path and all known details is as follows:
    ---------------------------------------------------------------------------------------

    -- Head --
    Stacktrace:
    at bxq.b(bxq.java:147)
    at bxq.b(bxq.java:125)
    at bxf.a(SourceFile:368)
    at bsu.a(SourceFile:809)
    at bsu.aj(SourceFile:465)

    -- Initialization --
    Details:
    Stacktrace:
    at bsu.a(SourceFile:299)
    at net.minecraft.client.main.Main.main(SourceFile:120)

    -- System Details --
    Details:
    Minecraft Version: 1.8
    Operating System: Windows 8.1 (x86) version 6.3
    Java Version: 1.8.0_45, Oracle Corporation
    Java VM Version: Java HotSpot(TM) Client VM (mixed mode), Oracle Corporation
    Memory: 108658168 bytes (103 MB) / 201539584 bytes (192 MB) up to 523501568 bytes (499 MB)
    JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx512M -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
    IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
    Launched Version: The 5zig Mod-2.4.1_1.8
    LWJGL: 2.9.1
    OpenGL: AMD Radeon R7 200 Series GL version 4.3.12618 Compatibility Profile Context 13.251.9001.1001, ATI Technologies Inc.
    GL Caps: Using GL 1.3 multitexturing.
    Using GL 1.3 texture combiners.
    Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported.
    Shaders are available because OpenGL 2.1 is supported.
    VBOs are available because OpenGL 1.5 is supported.

    Using VBOs: No
    Is Modded: Very likely; Jar signature invalidated
    Type: Client (map_client.txt)
    Resource Packs: []
    Current Language: English (US)
    Profiler Position: N/A (disabled)


     
  2. Offline

    EvilWitchdoctor

    From the crash report it looks as if you're running a modded minecraft. I'd suggest starting it in vanilla or reinstalling the game (remember to back up any singleplayer worlds). If the problem persists then it may be that your java is out of date or improperly installed. To be honest, I don't think you getting banned was the cause, but perhaps someone from the server planted a bug in your game through a texturepack or mod? I'm not really sure if the first one is even possible but I like to be open minded.
     
  3. Offline

    Boomer

    Its a corrupted json file, and most likely, fix 1 will solve it.
    [​IMG]
     
Thread Status:
Not open for further replies.

Share This Page