Occasionally, mod developers upload the same version of a mod to both Modrinth and CurseForge, but with some slight variation. This results in the file hashes not matching. Other times, some devs forget to upload to one or the other. Currently, that can be worked around by putting the mod .jar in the overrides folder but that introduces the need to manually track that mod's updates.
My suggestion is to add an option to the modlist.json's files to specify overrides for a specific target on a per-file basis. For example:
{
"project": "2M01OLQq",
"file": "nGPvABlf",
"side": "client",
"locked": false,
"overrides": {
"curse": {
"nGPvABlf": "shulkerboxtooltip-fabric-5.1.8+1.21.1.jar"
}
}
}In that instance, the shulkerboxtooltip-fabric-5.1.8+1.21.1.jar file in the overrides wouldn't be added as an override to a Modrinth modpack, but would in a CurseForge modpack. Mapping the .jar to the file ID would mean when the file ID is updated, the override would no longer apply and the CurseForge target build would fail, alerting to the mod(s) that need to be manually updated.
There may be a better method to accomplish the same concept; that one's just off the top of my head.
Occasionally, mod developers upload the same version of a mod to both Modrinth and CurseForge, but with some slight variation. This results in the file hashes not matching. Other times, some devs forget to upload to one or the other. Currently, that can be worked around by putting the mod .jar in the overrides folder but that introduces the need to manually track that mod's updates.
My suggestion is to add an option to the modlist.json's files to specify overrides for a specific target on a per-file basis. For example:
{ "project": "2M01OLQq", "file": "nGPvABlf", "side": "client", "locked": false, "overrides": { "curse": { "nGPvABlf": "shulkerboxtooltip-fabric-5.1.8+1.21.1.jar" } } }In that instance, the
shulkerboxtooltip-fabric-5.1.8+1.21.1.jarfile in the overrides wouldn't be added as an override to a Modrinth modpack, but would in a CurseForge modpack. Mapping the .jar to the file ID would mean when the file ID is updated, the override would no longer apply and the CurseForge target build would fail, alerting to the mod(s) that need to be manually updated.There may be a better method to accomplish the same concept; that one's just off the top of my head.