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.
Every time a new Minecraft version comes out, I have always been faced with the same exact problem: transferring my mods, settings, worlds, saved servers, etc, to the new version. This requires me to create a new installation, reinstall all mods, copy paste settings, stats, etc, double-check I havent forgotten everything, triple-check I havent forgotten anything, trying to play just to discover a mod is missing, and etc... Doing this, is genuinely a pain and takes a whole afternoon to do so.
Describe the solution you'd like
What I think would be the best solution for this, would be to add another button when creating an installation: "Update another installation".
This would let you choose an installation that you already have, select if you want to save mods, worlds, saved servers, resourcepacks, etc, then select what version you'd want to update the installation to, optionally letting users also change between different mod loaders, and then creating a clone of said installation with the selected parameters, with all the mods, resourcepacks, worlds, etc, properly transferred, updated, and converted incase the updated version requires modifying file structures or etc. For the mods, resourcepacks, and datapacks that dont have any available versions for the new installation, maybe let it create a new category (on the bar with Content, Files, Worlds, Logs, and Share) and folder in the installation, named "Incompatible Files",
where these files would be stored so that the players can view them and remove then from the folder. When the files eventually get an update compatible with the instance, let the user update these mods and use them. Let players use resourcepacks even if they arent compatible, as most of them generally work with most Minecraft versions.
Describe alternatives you've considered
I have tried using modpacks, where I create one out of the original installation, create a new installation with this modpack, change the Minecraft version, and then updating everything. This is a solid option... if we completely ignore the fact that all incompatible mods will remain there, with no way of identifying them. I could look at the error logs when starting the installation, and remove the mods it says are incompatible. But this is still an inconvenient and not so efficient solution.
I also think that collections could be transformed as a modpack-style feature, where you just create the mod list, then install it in an instance. This could also be great... but then there'd be no way of saving configs, data, worlds, saved servers, etc.
Additional context
No response
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.
Every time a new Minecraft version comes out, I have always been faced with the same exact problem: transferring my mods, settings, worlds, saved servers, etc, to the new version. This requires me to create a new installation, reinstall all mods, copy paste settings, stats, etc, double-check I havent forgotten everything, triple-check I havent forgotten anything, trying to play just to discover a mod is missing, and etc... Doing this, is genuinely a pain and takes a whole afternoon to do so.
Describe the solution you'd like
What I think would be the best solution for this, would be to add another button when creating an installation: "Update another installation".
This would let you choose an installation that you already have, select if you want to save mods, worlds, saved servers, resourcepacks, etc, then select what version you'd want to update the installation to, optionally letting users also change between different mod loaders, and then creating a clone of said installation with the selected parameters, with all the mods, resourcepacks, worlds, etc, properly transferred, updated, and converted incase the updated version requires modifying file structures or etc. For the mods, resourcepacks, and datapacks that dont have any available versions for the new installation, maybe let it create a new category (on the bar with Content, Files, Worlds, Logs, and Share) and folder in the installation, named "Incompatible Files",
where these files would be stored so that the players can view them and remove then from the folder. When the files eventually get an update compatible with the instance, let the user update these mods and use them. Let players use resourcepacks even if they arent compatible, as most of them generally work with most Minecraft versions.
Describe alternatives you've considered
I have tried using modpacks, where I create one out of the original installation, create a new installation with this modpack, change the Minecraft version, and then updating everything. This is a solid option... if we completely ignore the fact that all incompatible mods will remain there, with no way of identifying them. I could look at the error logs when starting the installation, and remove the mods it says are incompatible. But this is still an inconvenient and not so efficient solution.
I also think that collections could be transformed as a modpack-style feature, where you just create the mod list, then install it in an instance. This could also be great... but then there'd be no way of saving configs, data, worlds, saved servers, etc.
Additional context
No response