Quote:
|
Originally Posted by danlisa
 Please remind me the next time I decide to 'edit' a few cfg's to make them JSGME ready. |
Well considering that it is no secret that not only will there be a January patch, there will also be a major release mid-year, this will be a *very* good idea.
But if you use SH3Cmdr, why don't you just add the tweaks to its cfg files (like Static settings.cfg) instead? Then they'll be added every time you run SH3Cmdr and removed every time you roll it back (thus always keeping your game files in their original state). That's what I do...much less hassles.
Quote:
|
Originally Posted by danlisa
How clean will this GWX installation have to be? Are we talking 'squeaky' or will the installer be smart enough to tell you which file is the problem?
I know we've had this discussion before and I'm sorry to bring it up.
|
Yes, you should be sorry.
Last time there was needless and unnecessary dramas and stress over how the installer would work. In the end, was there anything to worry about?
If people just relaxed...
Anyway, the verification won't be as stringent this time. However, the intent is still to provide a stable addition over a stable GWX platform (hence why JSGME is not the best solution - just compare the number of "How do I install GWX?" questions to the number of "How do I install the Dec patch?" questions to see why).
This time the installer won't be explicitly looking for a valid 1.4b SH3 installation - that was done as part of the original GWX installation. This time it will be looking for some digital fingerprints that are unique to GWX. These fingerprints are in some of the key/core files and won't exist if subsequent third-party mods are installed.
What I am saying is, in much the same way virus scanners use heuristic algorithms to determine whether files contain viruses, the installer will use similar algorithms to determine whether *
your* installation will be compatible with the patch. If not, you will be advised of the files that failed.
It won't always get it right (a general side effect of this approach), but it will mean that the installer WON'T fail because you manually bumped up your renown in Basic.cfg.
It WILL also recognise and accept any "official" release of GWX, in other words, GWX with or without any or all of the subsequent "official" hotfixes. It's pretty smart.
It WILL instantly fail if it finds
any mods installed via JSGME, as they tend to be larger in size thus having the potential to cause more conflict. So at a minimum players will be expected to a) rollback SH3Cmdr and b) disable all mods prior to running the installer. But this is nothing new or unique.
The installer *may* even do an SH3Cmdr rollback check as well as a JSGME check, but we'll see.
In the end, the aim of the installer verification is simply to save YOU the pain of having to uninstall and reinstall SH3 and GWX because you forgot to remove that crucial game changing mod before installing the patch. Get it right beforehand, and just like the GWX installer, you won't even know what's happening behind the scenes and you'll have the patch installed in four or so easy mouse clicks.