Minecraft version

1.21.1

Describe the bug

Change the way of handeling duplicated mods. Current is confusing.

Steps to reproduce

Add two versions of the same mod with identical mod IDs but different file names (e.g., mod-1.9.jar and mod-1.91.jar). Mod mod-1.9.jar will be loaded which is confusing.

Logs

Additional context

When Sinytra Connector encounters duplicated mods (mods with the same mod ID but different versions or file names), it sorts mod JAR names alphabetically and processes them one by one, ignoring duplicates after the first occurrence. This results in a somewhat random version being loaded due to alphabetical sorting quirks (e.g., "1.91.jar" is treated as less than "1.9.jar"), with no clear logic or user feedback about which version was chosen.

In contrast, Fabric employs a sophisticated system of comparators to resolve duplicate mod IDs, applying various conditions to determine the "higher" version. While this avoids an immediate crash, it’s overly complex, varies across versions, and can still feel opaque to users. Sinytra Connector’s current alphabetical sorting approach is simpler but lacks intentionality, as the loaded version hinges on arbitrary file naming rather than a deliberate selection process. This can lead to confusion of users.

Suggestion:
I propose to crash the game when duplicate mod IDs are detected, rather than loading a version based on alphabetical JAR sorting. The crash message should include a list of the duplicated mods (e.g., their file names and paths) to help users identify and remove the conflicts. This would provide a clear, no-nonsense way to handle duplicates, avoiding the randomness of alphabetical sorting and the complexity of Fabric’s comparator system.