I am trying to get several mods working, but am having a problem with Forge vs ModLoader.
When I first upgraded to 1.3.2, I learned about how the 2 utilities are incompatible with each other, but also about how Forge has Modloader included in it, so the problem then was rather self-solving: just install Forge & I'll have both, so any mod can theoretically work that requires one or the other.
But now we're into 1.4.5, and things are different again. I took quite a bit of time trying to get SinglePlayerCommands installed (which is one of the absolute top priority mods for me), and in the end it turned out that the problems I had were because SPC is incompatible with Forge & requires ModLoader instead. So I exchanged one for the other, and it worked.
But now I'm also trying to install Enchantment Plus (which has a REALLY USEFUL feature that I SERIOUSLY WANT), but it specifically requires Forge. I tried installing it with what I have but it didn't work (I use MagicLauncher, and the setup screen shows a red error message "No Forge").
IIRC, in the discussions on the SPC thread, people seemed to indicate that Forge was relatively useless in the current game version compared to ModLoader, but I can see that there are some mods that DO need it. For example I also have GuiAPI (which I needed in past versions in order to make some other mods work), and it also gets the "No Forge" error mssg in MagicLauncher. I don't think I'm using any mods now that need it, but AFAIK there might be some significant ones that will need it which I just haven't gotten to yet.
So what's the deal? Is there way to bridge the gap between Forge & Modloader? To somehow make my game able to run both mods that require one AND mods that require the other? Or they the "The Great Divide" of Minecraft Mods, making all mods that specifically require one automatically incompatible with all mods that specifically require the other? In 1.2.5 (when I first started playing), the two acted as a team and if you needed either then generally you'd have to use both. But things change so much with every 2nd-digit version update (i.e. 1.2.x, 1.3.x, 1.4.x, etc), and I have so much difficulty understanding the technicality of it all to begin with, that I honestly just can't keep up on my own.
Forge generally has the ability to load Modloader mods, I think the problem with the incompatibility is both Forge and SPC edit the EntityPlayer class (IIRC please someone correct me if I am wrong). Base class editing is quite dumb in my opinion, especially when APIs such as Forge and Modloader provide the needed hooks to do most things.
When I first upgraded to 1.3.2, I learned about how the 2 utilities are incompatible with each other, but also about how Forge has Modloader included in it, so the problem then was rather self-solving: just install Forge & I'll have both, so any mod can theoretically work that requires one or the other.
But now we're into 1.4.5, and things are different again. I took quite a bit of time trying to get SinglePlayerCommands installed (which is one of the absolute top priority mods for me), and in the end it turned out that the problems I had were because SPC is incompatible with Forge & requires ModLoader instead. So I exchanged one for the other, and it worked.
But now I'm also trying to install Enchantment Plus (which has a REALLY USEFUL feature that I SERIOUSLY WANT), but it specifically requires Forge. I tried installing it with what I have but it didn't work (I use MagicLauncher, and the setup screen shows a red error message "No Forge").
IIRC, in the discussions on the SPC thread, people seemed to indicate that Forge was relatively useless in the current game version compared to ModLoader, but I can see that there are some mods that DO need it. For example I also have GuiAPI (which I needed in past versions in order to make some other mods work), and it also gets the "No Forge" error mssg in MagicLauncher. I don't think I'm using any mods now that need it, but AFAIK there might be some significant ones that will need it which I just haven't gotten to yet.
So what's the deal? Is there way to bridge the gap between Forge & Modloader? To somehow make my game able to run both mods that require one AND mods that require the other? Or they the "The Great Divide" of Minecraft Mods, making all mods that specifically require one automatically incompatible with all mods that specifically require the other? In 1.2.5 (when I first started playing), the two acted as a team and if you needed either then generally you'd have to use both. But things change so much with every 2nd-digit version update (i.e. 1.2.x, 1.3.x, 1.4.x, etc), and I have so much difficulty understanding the technicality of it all to begin with, that I honestly just can't keep up on my own.
I don't remember them acting as a team, Forge simply required modloader to run.