Forge and other ModLoader APIs

[DigitalClark]

Hello dear users,

I know there are serveral related threads out there and I also know the answer myself, but I want to verify my thoughts by asking you the following:

I downgraded my Minecraft to 1.2.5 again because I like that version more, many more mods are compatible with 1.2.5 instead of 1.3.2. The way I always used my modded Minecraft was by installing ModLoader, ModLoaderMP, Forge and then AudioMod. Now I red that Forge loads the mods from ModLoader without installing ModLoader and also replaces AudioMod. That's fine. I also know that ModLoaderMP isn't compatible with Forge, but I always get it to run by installing it before Forge and it works. Now I want to ask you: Does Forge replace ModLoaderMP (I think not)? Can I use them together or are there any disadvantages?

Sorry for any mistakes in this text, I'm on my iPod touch.

 

Thanks, DigitalClark.

[Zero]

I'm pretty sure that no. Forge doesn't actually replace it. If it did, it'd be more compatible with it. From what I've read ModLoaderMP goes about what it does either poorly, or in a way that isn't ideal. So, it's more a (bad) design choice for mod creators to use MLMP instead of Forge. For actual compatibility instead of "Well, it doesn't explode... That's good", mod authors will need to migrate to Forge instead of ModLoaderMP.

 

I'm almost certain this is the case. I say almost as I have little to no knowledge of java code quite yet, and am going on what I've seen around the forum. All I've seen is that Forge has a built in replacement for Forge, and is not compatible with MLMP. Never saw any mention of them trying to bother trying to be compatible with it. So I'd say no.

 

I'm sure somebody more knowledgeable than me will come along soon to let you know for sure. 

[DigitalClark]

Thanks Zero for your reply!

  On 10/6/2012 at 2:07 AM, Zero said:

All I've seen is that Forge has a built in replacement for Forge, and is not compatible with MLMP. Never saw any mention of them trying to bother trying to be compatible with it. So I'd say no.

Don't you mean that Forge has a built in replacement for ModLoader? Well, I know that it shouldn't be compatible with MLMP and I believe all of you, but the strange thing is that it works if you just install MLMP before Forge... Now, that this normally shouldn't work, I think that there are any disadvantages and that I better do not use MLMP mods until they are ported to Forge... Well, I'm just going to reinstall Forge without ModLoader, ModLoaderMP and AudioMod and I hope that it will work... But it's strange, that it works...

 

EDIT: I've just red that Forge and MLMP are compatible with each other, but only in SSP. In SMP they'll conflict. I won't use ModLoaderMP mods now, I'll stick with Forge. Goodbye MLMP, hello Forge!

EDIT 2: I just decided stick with 1.2.5 until 1.4 is out and I use ModLoaderMP with Forge for SSP and for SMP only Forge. That does not conflict and works fine. Are there any disadvantages to use MLMP and Forge in SSP?

[LexManos]

Considering SSP no onger exists in 1.3, {I know you're stating 1.2.5} anything that still uses MLMP is pretty much on a dieing horse and they should switch.

On the client side MLMP is really minimal, it does a few things, but for the most part there is a compatibility layer on the client side, as long as you install Forge AFTER MLMP.

MLMP just simply doesn't do the job that it set out to do in a satisfactory manor {seriously the job is 90% copy/paste of ModLoader and they can't even do that u.u}

Which causes incompatibility between client and server mods, causing the mod devs more pain.

 

So ya, pretty much if you use a mod that uses MLMP go yell at them to move to a better system, it's actually less work for them in the long run.

[cow123]

modloaderMP works for me when I put it in first (before forge)