Cirom

As long as you know how to use it and don't use any of the built-in mods, MCPatcher is VERY reliable. Far more reliable than MagicLauncher, anyway, which somehow loads mods twice every time, which causes a bunch of incompatabilities. I prefer using MCPatcher to just WinRARing everything into the jar as it's easier to just remove one mod without having to reinstall absolutely everything. Say if I found a small mod is having incompatabilities with Optifine, I can easily remove it and repatch. Build 4.0.0 #200. That enough definition? I have a bunch of mods in my folder, and for a first few moments I thought it was BetterThanWolves which was causing it, but as the log turns out Forge isn't bothering to load that one. Still loading others, though. And now it's randomly deciding to ignore anything that isn't in the 1.2.5 folder. Still crashing, though. I don't know what's going on. I'll provide a list of what's in my mods folder when it isn't 6am. 1.2.5 folder's here though:

^ I would do that, but then it would cause incompatabilities with MCPatcher, which is far more reliable to use than Forge is being. And Forge is at the latest build. I literally only just (re)downloaded it. Unless it updated in the past 25 minutes, I doubt I'm using an outdated version.

Yeah, but it's loading literally everything in it. Even within folders, while it's only supposed to load mods in the "mods" folder, not within subfolders. It's just messing with MCPatcher and ModLoader compatability there. Like I said, it would be a good idea to have an option to remove this, as it's frustrating to have it load even the outdated stuff. >_< Got a crash, but not sure how it happened.

Forgive me if this is the wrong forum category, but I can't seem to find the RIGHT one for what I'm about to say. Right now Forge has to be the most annoying thing to get working with the mod setup I have right now. I've designed all my folders to work with MCPatcher's method. I have various folders in my "mods" folder called "1.3.2", "1.3.1", etc. I don't use the mods built-in to MCPatcher (I just use it to add mods normally), but Forge doesn't half try to be annoying when I use it. It's searching through EVERY FOLDER within "mods" and adding everything, (As opposed to just "mods" with ModLoader) This is especially annoying, as Forge is trying to add mods in old version folders (ie: 1.2.5, 1.3.1, 1.1, beta 1.7.3) which obviously aren't compatable, forcing it to crash. I just wish there were options to prevent this functionality within Forge, as it's just FRUSTRATING to try to run any Forge mods when Forge is just digging into folders it's not supposed to. >_< Usually, I just inject everything directly into the jar with MCPatcher, even the "mod_" mods. This usually works just fine with ModLoader and things similar. (How do you think it works in the first place? ) With Forge, no dice. It's just crashing constantly, and the MCPatcher logs are just vague about it. >_< Not to mention the crashes are extremely inconsistent. I can do one thing before and it crashes, and seemingly exactly the same thing later and it doesn't. It's too confusing! I just wish there was an option to stop Forge loading what it shouldn't. >_<