More modloader support across curse without being required to use forge.
Options to chose between modloaders and supported mods/modpacks such as FabricAPI, liteloader, rift and so on.
Each modloader having it's own mods and modpack area as to not mix them up causing compatibility issues without including Forge as we are required to use at the moment (since that has been the only modloader on curse for a long time now)
Thank you for the suggestion, we are looking into this. Please add any additional details that you think would be helpful in the comments! We are Listening!
This is the most upvoted suggestion on the site and it has been suggested 2 years ago. There is simply no excuse for the extreme delay of the implementation of this feature. It would be fairly easy to implement (add Fabric version support to the CurseForge app and maybe Rift) and it's vital. If CurseForge doesn't move on with the community, the community will move on without CurseForge.
There's no excuse for this functionality not having been properly implemented by now. I should not have to see mods for a loader I don't use OR a version of the game I don't play.
Just add a simple filter for Forge or Fabric.. when I'm looking for mod updates I'm looking for Forge, I don't care to see Fabric. Filter the same way you do for version of minecraft. Simple drop down, Fabric, Forge, Both, Neither. IE, I need the ability for example to search for Forge only with version 1.16.2 of minecraft. Forge/Fabric should not be an option in the version selection.. I don't want to see 1.15.x mods.
So this is just never happening, right? Man, we really need a better site than this with how poorly it's run.
At this point, with huge mods like Tech Reborn moving over to Fabric, this NEEDS TO BE A THING. NOW. Moreover, we need a proper filtering system both web-side and client-side, not just one that lets you just pick one category to show exclusively, but one that actually lets you exclude categories or pick multiple to show. This is BASIC FUNCTIONALITY that has been absent from both CurseForge and the Launcher for far too long.
If you added a modLoader selection box where you have the Game Version, Sort By and Search, it would solve the problem. Adding the modloaders to the Game Version drop down is pretty useless as you can no longer filter by game version and you spend ages looking at mod that are for different versions of the game.
Coming up on a year since this was marked as "planned". Are there any updates?
Now that this is implemented on the website, I would like to have the option to have installs in the Twitch app use Fabric as well. (Also mod packs)
I would love at least a sort option for Forge mods. As it is now the forge mods are unfilted and are fabric mods are thrown in.
It's very imperative for the distinction to be made.
Another HUGE issue: stop setting a FORGE mod as the "main" download EVERY time. Curseforge does this even if the Fabric version is MONTHS newer (and for a more current version of Minecraft).
This happens every time a mod has versions for both Forge and Fabric.
There really isn't any getting around it anymore, this is absolutely necessary. You can talk about not wanting to support loaders that might go away in the future all you want, but the lack of this feature is the main thing preventing Fabric from getting the support from users that it needs to really be 100% secure in that.
One solution would be to tag at the file level, just like thay are tagged with MC versions. Just add a ModLoaderType tag and let devs tag their files one by one
In other words handle modloader just like MC versions for each file are handled now.
And of course expose that to the user on the site, at the file level
There is already an enum for ModLoaderType lost somewhere in the Curse API/Code, so it seems at one point there was an attempt to tackle this
Any updates on supporting loaders such as fabric i have mods that depend on it
Although it would be nice to be able to sort between forge, liteloader, and fabric mods, curse does support all of them just fine, they all go in the mods folder, thought unlike liteloader, fabric doesn't work with forge.
I like the fact that fabric updates frequently, but that's only because of how little code there is, the mods almost require code injection which is not a good idea unless it's the only option, and with fabric it almost always is.
It's now more than four months since this post has been marked as "under review".
Can you give any updates on the current status of this topic?
Daniel She commented
It has been nearly 3 months since the proposal, Fabric now has over 100 mods and it would be appreciatable to have fabric supported.
This is something that the new dashboard has proved is beyond necessary. Twitch Launcher downloads account for 90-95% of most mods' downloads, so preventing access to Fabric through the Twitch launcher means that people who target Fabric are screwed out of getting almost 19 out of every 20 Curse points they should be.
Raph Hennessy commented
It would be amazing if you could add at least Fabric support to Curse, since the main thing limiting its popularity at the moment is it's incompatibility with the Twitch launcher.
Any Updates about this? with Forge 1.13 and 1.14 Releasing Soon. I would love to know the direction CF plans to take with this.