Allow installation of mods from mismatching loader in client
This is regarding Minecraft modpacks - Recently, we've seen the rise of Quilt and NeoForge, because of internal issues that stemmed from the Fabric and Forge teams respectively. CurseForge has added integration for both of these modloaders. However, the issue currently is that the client restricts the installation of mods based on the loader your modpack is set to.
Currently, NeoForge is able to run mods that are made for Forge and Quilt is able to run mods that are made for Fabric. This should effectively broaden the scope of mods available for both loaders by a lot. However, in practice, it is annoying to put together a modpack for either loader unless the mod authors have specifically uploaded separate files for all 4 loaders, meaning CurseForge is storing redundant copies of every version of every mod.
Please remove this restriction. It would make sense to have a warning message or something, but please allow us to download any version of a mod from within the client, instead of having to manually download from the web.
-
Guest
- Jul 4 2024
- Future consideration
Related ideas
To add to this, there are some compatibility bridge mods for loading mods from a different loader.
Rather than having strict restrictions on installing mods for the "wrong" loader, it would be better to have profiles greyed out, but still selectable, and simply have a confirmation pop-up warning the user that the mod is for a different loader, and asking them to confirm that they know what they're doing. With multiple warnings, nobody would be installing mods on a different loader unknowingly. Meanwhile, people who are trying to do so on purpose won't have to go through the inconvenience of either downloading and installing manually (meaning needing to also keep track of dependencies), or creating a dummy profile to install mods to in order to transfer them over.
I second this. It take so long to go through every mod to see if it's compatible with each other. As Quilt and NeoForge is quite new, it will also take time for developers to add the needed code for each loader. As it's quite easy to see if they are compatible, I can't see that it can be the hardest thing to allow us to download the mod. Look at FTB Ultimine as an example .. made for Forge .. works fine on Neoforge .. but you can't download it in your Neoforge Mod Loader. Copying from my Forge loader works fine... it's just alot more work just to get the mods we want.
Implement a check for "what loader is it compatible with" and then open for download.