Please confirm the following.
What parts of Modrinth is your feature request related too?
No response
Is your suggested feature related to a problem? Please describe.
list containing just 20 mods and 20 libraries looks cluttered and is difficult to navigate quickly
Describe the solution you'd like
Mod Organizer 2 allows you to create your own categories—for example, separating libraries and mods into two groups based on their creators. Vortex offers similar functionality. Modrinth, however, does not support this; as a result, even a list containing just 20 mods and 20 libraries looks cluttered and is difficult to navigate quickly.
Vortex uses a hard-link method. I think this is possible because the JAR filenames are unique.
I propose using the hard link method. This entails keeping the mods folder unchanged while simultaneously creating a separate mechanism that links the JAR files to the interface via hard lilink.
Describe alternatives you've considered
No response
Additional context
A similar situation is described in issue #4234; however, that case involves a change to the mod handling mechanism, which requires adaptation by either the launcher or the mod loaders.
For this method, I propose naming the modifications by combining the original name that was added in mod page and version of this mod with, for example, a four-digit code for standardization
Please confirm the following.
What parts of Modrinth is your feature request related too?
No response
Is your suggested feature related to a problem? Please describe.
list containing just 20 mods and 20 libraries looks cluttered and is difficult to navigate quickly
Describe the solution you'd like
Mod Organizer 2 allows you to create your own categories—for example, separating libraries and mods into two groups based on their creators. Vortex offers similar functionality. Modrinth, however, does not support this; as a result, even a list containing just 20 mods and 20 libraries looks cluttered and is difficult to navigate quickly.
Vortex uses a hard-link method. I think this is possible because the JAR filenames are unique.
I propose using the hard link method. This entails keeping the
modsfolder unchanged while simultaneously creating a separate mechanism that links the JAR files to the interface via hard lilink.Describe alternatives you've considered
No response
Additional context
A similar situation is described in issue #4234; however, that case involves a change to the mod handling mechanism, which requires adaptation by either the launcher or the mod loaders.
For this method, I propose naming the modifications by combining the original name that was added in mod page and version of this mod with, for example, a four-digit code for standardization