What I mean is there are mods that are already approved for say forge. . . then that same creator makes a fabric port but it doesn't get approved. . . enough though it's the EXACT same mod but just more compatible???
Popularity shouldn't matter for ports of a mod by the same creator where the original mod was already popular and approved.
An example I found was:
https://www.curseforge.com/minecraft/mc-mods/bountiful
vs
https://www.curseforge.com/minecraft/mc-mods/bountiful-fabric
BOTH are made by the same guy, only difference is one is a newer version.
I get the staff of this site doesn't want to risk it with new untested stuff. . . But creators like this ALREADY proven to you that they know what they are doing with the mod that you already approved for another instance. The "suggestion" system needs to be updated to account for "official ports".
Here is the MAIN issue:
If they upload this file to the SAME mod page as the forge version, but still be a fabric version. . . it would already be approved because it's the same mod.
As it stands now, this system only serves to punish mod developers for giving their mod separate pages for forge vs fabric loaders. This needs to be addressed.
Solution:
When a mod fails to verify, give users the a second option of "Is this mod an official port of another mod? if so, link the original mod here:" where it checks to see if the owners match up between the original mod and the port and then it gets sent in for review by a human, not an automated system. Either that, or allow mod developers to connect their mod account (curseforge or alternative) to their aternos account so that they can manage ports of already approved mods themselves and thus do the work for you of saying "it's the same mod".
Please stop punishing mod developers for making a separate page for their fabric/forge versions. You are only forcing a loophole of them uploading both to the same page by doing this and this forced loophole doesn't help you, the mod developers, your curation system, the users here. . . it unfortunately only serves to get in it's own way.
It's not a new mod, it's a new version of the same mod. If it was on the same page, it would already would allow any new versions after the first version of a mod is approved. It shouldn't be any different just because it's on a new page. This is an issue with your mod suggestion system that needs to be fixed.