EDIT: Actually my analysis was wrong, I updated it

I thinkUpdateLocatorIds(loadout) might need to go before theawait ActivateLoadout(loadout); (L1144) during the loadout switching code.

Otherwise if there was a game update, and the user tries to switch to a different target loadout we would:

• Correctly deactivate the previous loadout, updating itsLocatorIds, ingesting any changes.
• Reset the game to the gameMetadataLocatorIds, which should be the latest ones due to the previous Synchronize.
• Try to Activate the target loadout against a vanilla game state that doesn't match the loadoutLocatorIds (still on the old game version).
• Likely run into missing backups exceptions because we no longer backup old game versions.

I think we should also update the target loadout to use the newLocatorIds as the base for now.

In the future, if we wish to allow users to select which Game version they wish each Loadout to be on, then we will have to add some extra data likeDesiredLocatorIds to be able to determine exactly which version we should want a loadout to be based on, but for now, I think going by what is provided by the game storeLocatorIds is best.

Might be something for QA to test, not sure if they have loadout switching between different game versions on their list.

Test case for cyberpunk would be:

• Unmanage game, close the app.
• In steam disable a DLC, run the game to ensure the change is applied.
• Open the app, manage the game (loadout A), add a couple of mods, apply.
• Create a second loadout (B), don't apply.
• Go in steam and enable the DLC again, run the game to ensure the change applied.
• Go back to the app
• Disable a mod in Loadout A, Apply. This should hopefully not backup the DLC.
• Now go to Loadout B and Apply that one
• Ideally this should work without exceptions and without backing up DLCs either.