Help: Minecraft hangs on Mojang Logo

  • Yeah, like the title says, I've been having trouble with IC^2. I added all of the prerequisites before hand: Modloader, ModLoaderMP + Fix, and MinecraftForge (I also installed Audiomod for Equivalent Exchange).


    I launched Minecraft through the linux terminal after hanging a few times, and I got this:




    Any help? I made sure to get all of the latest versions.


    Mods installed:
    Pre-reqs (ML, MLMP+Fix, MCF, AudioMod)
    IC2
    Timber
    Wireless Redstone
    Equivalent Exchange
    Recipe Book
    TF2 Teleporter
    TooManyItems (Testing purposes)
    Advanced Solar Panels
    Charging Bench</init>

  • Downloaded a fresh jar, wiped all of the mods I had, redownloaded ModLoader, MLMP and the fix, Forge and IC2 only. Installed the pre-reqs into the jar, created a 'mods' folder and placed the IC2 jar in there. I reran it via terminal, same error:


    </init>


    </init>
    EDIT: Alright, I know it's not IC2 giving me the error, just installed the prerequisites; above error.</init>

  • Brilliant... I installed ML, MLMP, MLMP Fix, Forge, deleted the 'paulscode' folder, installed the fix (as per another topic) and still epic load time.


    And the same error from the Terminal as above.


    Judging by the error, it's something on Modloader's end, half considering hopping over to Risugami's thread and asking about it.

  • Is there a ModLoader.class in minecraft.jar? If not your zip utility is broken (like Ubuntu's archive manager for example)

    Dammit. Modloader.class ain't in there. Thanks, give me a few to do some extracting+adding+rezipping and I'll edit this post with the specifics.


    EDIT: Archive Manager hates me. I extracted a fresh jar, unzipped Modloader, cut and pasted the files over, re-archived the jar. Launched the game, nothing. Ran via terminal, same error. Looked inside the jar, no Modloader.class.

  • Can a mod lock this? The error lies on Modloader's side of the equation, so I'm squatting on that thread to see if a fix or something will come along.


    I found the fix, turns out the Ubuntu Archive Manager messes up and places the ModLoader.class inside a '/java/lang/' directory inside the jar. Just cut and pasted into into the root of the jar.


    FIXED