Please confirm the following.
What parts of Modrinth is your feature request related too?
Modrinth.com website
Is your suggested feature related to a problem? Please describe.
I have a mod (allium) that does not depend on the game. Its only hard dependencies are java version and mod loader version. The problem is every time a new game version comes out I have to modify the mod version's metadata, adding the game version.
Describe the solution you'd like
I assume versions on the backend could be supported to have a java version associated with them, such that versions of allium could be pinned to it, then any game version that comes out with a java version that is greater than or equal to the pinned java version are added as supported game versions for that version. This feature would also be beneficial for language adapters.
Describe alternatives you've considered
My suggestion is a scoped down idea that supports my use case. Really, the whole version selection system could be made richer, like supporting:
- version range strings ex. ~26.1, >=1.20.1, etc.
- java versions like I suggest here
- loader versions (with ranges like suggested above)
Additional context
No response
Please confirm the following.
What parts of Modrinth is your feature request related too?
Modrinth.com website
Is your suggested feature related to a problem? Please describe.
I have a mod (allium) that does not depend on the game. Its only hard dependencies are java version and mod loader version. The problem is every time a new game version comes out I have to modify the mod version's metadata, adding the game version.
Describe the solution you'd like
I assume versions on the backend could be supported to have a java version associated with them, such that versions of allium could be pinned to it, then any game version that comes out with a java version that is greater than or equal to the pinned java version are added as supported game versions for that version. This feature would also be beneficial for language adapters.
Describe alternatives you've considered
My suggestion is a scoped down idea that supports my use case. Really, the whole version selection system could be made richer, like supporting:
Additional context
No response