Adding an option to update all mods to their correct versions after changing the Minecraft version of an instance
Is your suggested enhancement related to a problem? Please describe.
Let's say I use a modpack in Minecraft 1.20.1 with Fabric, and decide to switch it to the newest Minecraft version, 1.20.2. To do that, I first have to switch the game version in the modpack's options. However, after this, there is no option to update the mods to 1.20.2, or to show which ones don't officially support this minecraft version. The "update" button does not update the mods to 1.20.2, but to their latest 1.20.1 version, even after the minecraft version of the instance has been changed, which makes little sense. This means I have to manually click on each mod, go to the "versions" tab, and manually switch the version to 1.20.2, or to remove the mod if it has no 1.20.2 version. Depending on the amount of mods used, this can take an extremely long time.
Describe the solution you'd like
After changing the minecraft version of a modpack, and going to the "Content" tab, I should be prompted with a message saying something like "The minecraft version of this instance has been changed. Do you want to update the mods to 1.20.2?" "Yes / No" The app would then check if the mods support 1.20.2, and update the ones that do to their official 1.20.2 version. If there are mods without official 1.20.2 support, a dialog box would appear saying "These mods do not have official 1.20.2 support, starting the game with them still installed could cause crashes or prevent the game from launching. Do you want to remove them?" along with a list of which mods don't support the version, where you could also select specific ones to remove.
This would make the process of updating a modpack to a newer version of minecraft significantly easier and less time-consuming. The reason I am submitting this feature request is because I imagine it would be a pretty easy process to automate. Indeed, either the mod has a version that supports 1.20.2 in the "versions" tab, or it does not. It shouldn't be for the user to manually check if each mod has one or not. Of course, some mods without official 1.20.2 support could still work. Then and only then should it be for the user to test each one manually if they want to.
Describe alternatives you've considered
I think it could be an option to have one more dialog box that says "These mods only support 1.20.2 in their preview versions. These versions are in development and may contain more bugs than usual. Use preview versions?". A list of these mods would also appear, indicating whether they are in alpha or beta, and you could also select specific ones to install.
Additional context
No response
This would be a super useful feature, is there any chance is gets implemented?
It's sort of already a feature, you can just hit update all
The chances that's going to simply work are really slim though
I've already had this issue, it would be pretty good if it was added but wont be useful to many people
I've already had this issue, it would be pretty good if it was added but wont be useful to many people
it would be pretty usefull to A LOT of people especially if you want to keep up with versions
Maybe the app should automatically update content upon version/loader change
And if there are no versions of that mod compatible, it should have a popup saying which mods will be disabled.
This is absolutely needed, and would safe us hours.
A simple fix is to make the filters available in the explore tab available within modpacks, or at least add an option to filter by version