Hello, first post here.

 

I have virtually no experience whatsoever creating those error/bug report files that this forum requires for bug reports, so bear with me for the moment.

 

I use MCPatcher 2.3.7_01 to patch ModLoader 1.2.5 and Forge 3.2.5.120 client version. Patching ModLoader without Forge yields the desired results (Minecraft works). Patching Forge after ModLoader and running Minecraft from the Test Minecraft button in MCPatcher causes Minecraft to get stuck at the white screen just before the Mojang logo. Running Minecraft from its .exe (which prompts the Minecraft login) gets the game stuck at the black screen before the Mojang logo. There are no crash or error messages, the game simply stops responding. I can close it just fine.

 

I'm pretty sure I'm using all the latest versions of everything. I have used official download links from this forum and from minecraftforum.net, redownloaded and repatched numerous times (up to and including wiping my .minecraft folder repeatedly).

 

The following conflict warning is displayed by MCPatcher when patching Forge onto ModLoader:

 

 

ModLoader 1.2.5

MinecraftForge-3.2.5.120-Client

    BaseMod.class

    MLProp.class

    ModLoader.class

    ModTextureAnimation.class

    ModTextureStatic.class

    adl.class

    ahg.class

    ahu.class

    ahy.class

    ajv.class

    alb.class

    alj.class

    amn.class

    fq.class

    ko.class

    uu.class

    vl.class

    vx.class

Only the files from MinecraftForge-3.2.5.120-Client will be used.

 

 

What am I doing wrong? Aside from not spitting out reams of error logs at you guys.

 

--Tuan

1) You're using MCPatcher, that isnt supported nore does it work.

2) You're not posting the error log, cuz there is always a error log. Unless there is a major hardware issue with your computer that has nothing to do with Forge. There is always a log.

It's interesting that you say that MCPatcher isn't supported nor does it work, because older versions of MCPatcher, ModLoader and Forge have played just fine together on my computer. In fact, MCPatcher has been pretty essential for me to make what few mods I use install easily without hitching up the gameplay. Must've been coincidence, then.

 

Oh well. Let's hope Minecraft 1.3 shows up with due haste.

 

--Tuan

I advise a wonderful program called 7zip for installing Mods, or MultiMC, or MagicLauncher, or the plethora of other ways to install mods properly.

MCPatcher does some horrible things even if you disable all of it's internal mods it will edit some classes for itself causing error.

Due to this... behavior, we do not support it in any way. It is a good concept, but, needs to work better.

Aside from the fact that WinRar already does everything 7zip does, which completely excludes a non-migrainy mod installation route, I suppose I'll look into these MultiMC and MagicLauncher. Hopefully they also support HD texture packs.

 

--Tuan

They don't, but Forge does, and if you want extra features, Optifine.

There is NO reason to use MCPatcher.

Okay, so I got Magic Launcher.

 

And when adding MinecraftForge-3.2.5.120-Client.zip in the Setup, Magic Launcher states that it's not compatible.

 

Do you want detailed bug reports, and how do I attain them in that case?

 

--Tuan

Haven't used MagicLauncher for a while, but, there should usually be a console window or something when you try to run the game. Dig around in it.