Automatically remove invalid dlc and updates as part of auto load #42
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "auto-load-remove-missing-updates-and-dlc-files"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Automatically remove missing dlc files and update files as part of auto load and notify user of missing items
Fixed some minor label spacing issues in options dialog
Removal of unused variable in input view model
@ -736,3 +737,4 @@
"AutoloadUpdateRemovedMessage": "{0} mises à jour manquantes supprimées",
"ModWindowHeading": "{0} Mod(s)",
"UserProfilesEditProfile": "Éditer la sélection",
"Cancel": "Annuler",
I think this was removed by mistake? Or was it kept by mistake in the other locale file?
@ -736,3 +737,4 @@
"AutoloadUpdateRemovedMessage": "{0} mises à jour manquantes supprimées",
"ModWindowHeading": "{0} Mod(s)",
"UserProfilesEditProfile": "Éditer la sélection",
"Cancel": "Annuler",
Hey @GreemDev,
Great pick up! Would you believe I checked these code changes 3 times before committing LOL
I have reinstated this message now, apologies for missing this.
Thank You.
Download the artifacts for this pull request:
GUI-less (SDL2)
Only for Developers
@amurgshere how would you handle situations where the user would want to use an older update of the game as an example a bug to exploit for speed running?
Hey @gh0sti ,
Just a note, I did not implement the original solution to auto select the updates and DLCs, I only improved it a little and fixed some minor issues. But the original author already thought of this scenario, the currently selected update will be retained as long as no new updates are found for that game / app, only if a new update is found for that game / app and it has a newer version then the currently selected one will it then switch to that one automatically, and if the user adds a new update to the folder with a later version then it would be implied that they want to update to it, if they don’t then they can always switch to the older one again, apart from this it should retain the older version being selected.
Also note that the user can choose not to configure any search folders for updates / DLCs and choose not to use this functionality at all if they want.
Let me know if you find it working differently to this.
Cheers.