Alfred Keitzer
03-06-10, 07:00 PM
Here’s a horrible thought I just had regarding mods for SH5. Not having bought SH5 yet, maybe someone who has can comment.
I’m sure most of you know how JSGME works for implementing mods. If a file is going to be replaced by a mod, the file is first backed up by JSGME to the !BACKUP directory, and then the operational file is replaced with the mod file.
Now as I understand it, Ubisoft does auto-updates to the SH5 program. So what happens if you’ve applied a mod and SH5 does one of its auto-updates and overwrites one or more of your operational mod files? It appears to me you now have two issues. First, JSGME thinks the mod is active when in fact one or more of the mod files has been overwritten by an auto-update. Second, if you uninstall the mod, the file will be replaced with that from !BACKUP, which is a pre-SH5 auto-update version.
Just seems like SH5’s auto-update and mod updates have the potential to step on one another big time!
I’m sure most of you know how JSGME works for implementing mods. If a file is going to be replaced by a mod, the file is first backed up by JSGME to the !BACKUP directory, and then the operational file is replaced with the mod file.
Now as I understand it, Ubisoft does auto-updates to the SH5 program. So what happens if you’ve applied a mod and SH5 does one of its auto-updates and overwrites one or more of your operational mod files? It appears to me you now have two issues. First, JSGME thinks the mod is active when in fact one or more of the mod files has been overwritten by an auto-update. Second, if you uninstall the mod, the file will be replaced with that from !BACKUP, which is a pre-SH5 auto-update version.
Just seems like SH5’s auto-update and mod updates have the potential to step on one another big time!