You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I checked the existing issues for duplicate feature requests
What parts of Modrinth is your feature request related too?
Modrinth App
Is your suggested feature related to a problem? Please describe.
When I update minecraft mods to a new version, I have to dig through each mod that didn't have an update to see if the author stated that the latest version of mc is supported.
An example is:
Mod dev released 1.4.1
Minecraft releases 26.3
Mod dev updates 1.4.1 metadata to support 26.3
In order to see that they updated 1.4.1 metadata, you have to go through versioning of mod to find it.
How I update mods in releases is this:
Duplicate an instance and rename it to new minecraft version (26.3)
Update instance metadata to use new minecraft and loader. (I use fabric)
Update all mods that have releases (not beta or alpha ones) to support 26.3.
- Modrinth app easily supports this, as when I change mc version, it checks to see if mods have updates fo r that version.
Go through (manually) each of the mods, and enable those that say they support 26.3.
Issue is here. I have to manually click on the mod, and look at its versions.
Describe the solution you'd like
In the filters (see image below), have it filter by what version of minecraft a mod supports. That way I can also set the filter to say both 'disabled' and 'supports 26.3' to see what mods I have disabled now support 26.3.
Describe alternatives you've considered
The only really alternative I can think of is:
Manually going through each mod's versioning and seeing if it supports 26.3 (what I do rn).
Please confirm the following.
What parts of Modrinth is your feature request related too?
Modrinth App
Is your suggested feature related to a problem? Please describe.
When I update minecraft mods to a new version, I have to dig through each mod that didn't have an update to see if the author stated that the latest version of mc is supported.
An example is:
In order to see that they updated 1.4.1 metadata, you have to go through versioning of mod to find it.
How I update mods in releases is this:
- Modrinth app easily supports this, as when I change mc version, it checks to see if mods have updates fo r that version.
Describe the solution you'd like
In the filters (see image below), have it filter by what version of minecraft a mod supports. That way I can also set the filter to say both 'disabled' and 'supports 26.3' to see what mods I have disabled now support 26.3.
Describe alternatives you've considered
The only really alternative I can think of is:
Additional context
This is a nice feature to have when updating, or changing mc version. I would consider this a Quality of Life.
Making a note that it could be called similar to #7367.