henryestanley14 Posted September 29, 2020 Share Posted September 29, 2020 title! Link to comment Share on other sites More sharing options...
dubiousintent Posted September 29, 2020 Share Posted September 29, 2020 (edited) Don't use it myself, so you might want to wait to see if someone with direct experience responds. But definitely not a dumb question. Much better than rushing ahead and trashing your setup. In the meantime: generally the term "update" refers to an "install new version to the same location as the currently installed version" process. This typically attempts to preserve the existing configuration files and folder structure, but a sufficiently large difference between versions (usually indicated by a new "primary version number": e.g v2.0 instead of v1.2) might turn into "no difference from a completely new install". However, in the particular case of NMM, it might depend upon whether or not you are attempting to update from a version which originally came from the Nexis site itself (which is no longer supported), or from the GitHub fork which is community supported. That should probably be considered as a "new install" for "safety's sake". The current Community "GitHub" NMM version has three numbers to it's system (v0.72.2): a "primary" or "release" of "0", a "secondary" or "features" version currently of "72", and a "tertiary/fixes" of "2". Tertiary updates are "bug fixes" and not going to change the basic structure. "Secondary/features" shouldn't either, but might "add" something to the existing structure. "Primary/release" changes are most likely to make changes requiring a "new install". (Always check the release notes first, though.) A "release number" of zero indicates (to me at least) that the GitHub version did not make any major changes to NMM when it was taken over by the community, which would have been a major goal at the time. (Primary/release numbers of zero typically indicate a "beta" version of the product.) However, this numbering system (and variations based upon it) is not "cast in stone", but simply a "best practice" used by professionals. In any case, best to make a backup of your existing NMM install folder first, and at the very least know where it is keeping your mod files and any "profiles" in case you do have to tell a "new install" where those files are located. -Dubious- Edited September 29, 2020 by dubiousintent Link to comment Share on other sites More sharing options...
henryestanley14 Posted September 29, 2020 Author Share Posted September 29, 2020 Don't use it myself, so you might want to wait to see if someone with direct experience responds. But definitely not a dumb question. Much better than rushing ahead and trashing your setup. In the meantime: generally the term "update" refers to an "install new version to the same location as the currently installed version" process. This typically attempts to preserve the existing configuration files and folder structure, but a sufficiently large difference between versions (usually indicated by a new "primary version number": e.g v2.0 instead of v1.2) might turn into "no difference from a completely new install". However, in the particular case of NMM, it might depend upon whether or not you are attempting to update from a version which originally came from the Nexis site itself (which is no longer supported), or from the GitHub fork which is community supported. That should probably be considered as a "new install" for "safety's sake". The current Community "GitHub" NMM version has three numbers to it's system (v0.72.2): a "primary" or "release" of "0", a "secondary" or "features" version currently of "72", and a "tertiary/fixes" of "2". Tertiary updates are "bug fixes" and not going to change the basic structure. "Secondary/features" shouldn't either, but might "add" something to the existing structure. "Primary/release" changes are most likely to make changes requiring a "new install". (Always check the release notes first, though.) A "release number" of zero indicates (to me at least) that the GitHub version did not make any major changes to NMM when it was taken over by the community, which would have been a major goal at the time. (Primary/release numbers of zero typically indicate a "beta" version of the product.) However, this numbering system (and variations based upon it) is not "cast in stone", but simply a "best practice" used by professionals. In any case, best to make a backup of your existing NMM install folder first, and at the very least know where it is keeping your mod files and any "profiles" in case you do have to tell a "new install" where those files are located. -Dubious- Thank you so much! Link to comment Share on other sites More sharing options...
Recommended Posts