We just need a method beyond the current subcategory. We need a new option for individual jars. I have Fence Jumper for both Forge and Fabric now, but under the same project. What is limiting Fabric atm is Curse/Twitch Desktop. If a pack dev were to make a pack, they should be able to specify the loader, and then be able to choose mods available on that loader. I completely skipped Rift as I saw the issues with it. Fabric is actually viable, and imo, MUCH better than Forge to dev for. There is no one central person everything has to pass through and they are really good at staying up-to-date with the latest snapshots, which gives us mod devs time to test and polish our projects before the official MC version drops. This allows us to have true testers before dumping buggy projects on the community. So, back to what I was saying: We NEED this to be a "per jar" option since I'll likely be maintaining projects for both loaders for the foreseeable future. This issue would/will be exacerbated if/when Forge releases for 1.14, where (with the current setup), it will appear on Twitch Desktop like there is an update available for a Forge mod. Then the user gets a crash, and us devs suffer the false reports.