BlueMap

BlueMap

85.1k Downloads

Split CurseForge project into separate Forge and Fabric projects

Kage-Yami opened this issue ยท 3 comments

commented

Is your feature request related to a problem? Please describe.
CurseForge wasn't built to handle competing mod loaders (Forge and Fabric), and so gets a bit funky these days when a mod supports both. In particular (depending on upload order, I think), the CurseForge client can download the wrong version for a given profile. For instance, it downloaded the Fabric version for me (pulling in Fabric API as well) when I'm in a Forge profile.

Thankfully, it's easy enough to manually switch the version, and then delete Fabric API, but it's a bit of a nuisance. To top it off, the CurseForge client now says there's always an update, because it thinks the Fabric version is newer than the Forge version.

Describe the solution you'd like
I suggest splitting the CurseForge project into two separate projects, each dedicated to either the Forge or Fabric versions. This should simplify downloading and modpack maintenance of the mod using the CurseForge client considerably. (As an example, Dynmap does this.)

Original suggestion on Discord

commented

Curseforge got updated to support the different modloaders, so as long files are marked correctly for forge/fabric they should work fine now.

commented

Sooo, i guess this can close :)
Thanks!

commented

Is your feature request related to a problem? Please describe.
CurseForge wasn't built to handle competing mod loaders (Forge and Fabric), and so gets a bit funky these days when a mod supports both. In particular (depending on upload order, I think), the CurseForge client can download the wrong version for a given profile. For instance, it downloaded the Fabric version for me (pulling in Fabric API as well) when I'm in a Forge profile.

Thankfully, it's easy enough to manually switch the version, and then delete Fabric API, but it's a bit of a nuisance. To top it off, the CurseForge client now says there's always an update, because it thinks the Fabric version is newer than the Forge version.

Describe the solution you'd like
I suggest splitting the CurseForge project into two separate projects, each dedicated to either the Forge or Fabric versions. This should simplify downloading and modpack maintenance of the mod using the CurseForge client considerably. (As an example, Dynmap does this.)

Original suggestion on Discord

I think this is a bug of CF client.