CurseForge should scan mod files for MCreator footprints due to the unreliability of the creators correctly tagging their mods
CurseForge already scans files to some degree, of course. Due to the rise in popularity of the MCreator software, more and more mods are being uploaded to CurseForge. I suppose it’s not exactly a bad thing or whatever. However, for people like myself who do not want to use MCreator mods of any kind, sometimes it’s hard to spot if a mod is actually made with MCreator or not because MANY mod authors will not tag their mods as “MCreator”. This is most likely due to the creators being unaware that this is an existing category on CurseForge, or they know that the mod will probably not get nearly as many downloads if it does have the tag.
Personally, I’ve found my solution to this issue, but it involves downloading the mod and opening it with WinRAR to see the mod’s contents and looking for the net.mcreator path in the source code. I do find this highly inconvenient, and I’d much rather not support MCreator mods, but that’s kind of the only thing I can do other than scavenge through comments to see if it is mentioned or not.
This SHOULD NOT apply to mods that have new non-MCreator mod files uploaded to their project page. I see many people who move on from using this software onto actual modding, so I personally don’t think they should receive the “MCreator” category/tag by default.
-
Guest
- Mar 26 2023
- Not planned
Related ideas
Maybe if you don't know how to use it or if you have a bug, contact their support instead of commenting on someone else's idea (that has nothing to do with you) who put time and effort to explain their suggestion (directed at the comment below)
Respectfully, I never had a good experience with this. Breaks my sims everytime I install even one mod through it. Instead of being worried about tags, yall should be worried about how unreliable the app actually is, thousands of broken mods almost to the point is obsolete.