(This is in the context of Minecraft, but if this could be implemented anywhere else then that'd be great)

Earlier I'd spent too long trying to clone my modpack to a newer game version. It gave me a selection, so I thought it was available. It would then fail to work and I sat there wondering if it was bugged, so I went to the curseforge-support channel... apparently it's not a bug! My modpack is very customised to my liking, many mod settings configured, quite large, etc. and although I was able to "copy" (some of) my mods + resource packs over by recording the list of content I had with my phone so I could easily find them all, it took so long, AND I still had to reconfigure their settings afterward (fortunately copy pasting folders made it easier).

I wonder why it gives you a drop-down selection of game versions if you can only clone using the same game version you're already using - personally, it's quite misleading. I do know, however, that a lot of mods from one game version may not work in another. But, to tackle that, I think that Curseforge could read the contents of the modpack you're using and show a list of all incompatible mods given to you as a disclaimer before you clone, with an icon next to them in your list after the conversion to tell you they aren't supported. This'll help identify the mods that need dealing with post-clone. Alternatively, Curseforge could show a disclaimer/warning with a list of incompatible mods that'll be auto-deleted (their dependencies as well, if they aren't also being used by a mod that won't be auto-deleted) if you proceed. Plus, similarly to the Crash Assistant mod, Curseforge could also send a report showing details when there's a mod conflict that prevents a start-up, whenever you try to boot up your instance.

This would make updating modpacks so much easier, rather than having to search far and wide for all 200+ mods... and then reconfigure them..