Known issue for collection curation in v1.11 involving FOMOD backwards compatibility

[insomnious]

Hello there curators! I wanted to reach out and just let you know what we've discovered since version 1.11 of Vortex went out. As you are aware, the big thing we worked on for this release was the requested feature of the comparison of patches and installer choices when installing a collection.

Since the release went out, it's highlighted a fomod installation issue which would of never been noticed before v1.11 when doing a clean collection install and completely ignored (due to the comparison not taking place) when a user updated a collection.

What we've worked out is that curators need to pay extra attention now to whether a fomod is backwards compatible between it's versions. The big issue is that newer installer options are trying to be applied to older installers and Vortex is getting stuck working out what to do.

For example: MyMod version 2 isn't backwards compatible with version 1 as installer options were changed or removed. When the collection is curated, the version `latest` can't be used as the installer options set for v1 won't work on v2. In this case you'd need to use `exact` so that v1 is always downloaded. If v2 is needed for the collection to work, then v2 will need to be specifically downloaded by the curator and installer options set accordingly before publishing.

This isn't really something we can _fix_ as it's down to the mod authors to make sure breaking changes are communicated effectively and also down to curators to make sure the right version settings are chosen (`latest`, `prefer` or `exact`). We do, however, always strive for Vortex to help where it can as a user just having a stalled collection installation isn't ideal, and the warning for curators when choosing `latest` is quite small and without much context. We have got a bugfix in testing which fixes a problem where installation options are cached until Vortex is restarted. 

Next steps for us that will help this are to update the dialog and warnings when curating to provide more information (as mentioned above) and if this incompatibility is found during collection installation, let the user know what happened and why. This is going to take us a bit of time and so I would recommend any curator with this type of issue since v1.11 came out to check any mods that seem to cause the collection to stall.

More details are on the GitHub issue, including workaround steps.

Regards,

insomnious