REAVER ==>But that breaks MapView and possibly other things I haven't discovered yet.
Meridian==>you copy files manually into protected directories without admin rights...
Yes, all my installs now go into created directories c:/games or c:/applications NOT default C:/program files since Windows VISTA and above cause mods to do funny things without administration tinkering with those folders.
I just clone my install and rename the OpenXcom folder before I run a new nightly.
Once I understood the .exe nightly is a "full install," sans xcom files; life was easier
IE (long version with example)
In the past, I have created the install location "c:/games/Openxcom"
I Rename the directory Openxcom to OpenxcomOldjune6_2017 (I have renamed original directory)
---
I get latest nightly and run its install process;
--original files are auto copied from UFO directory of where installed "Xcom UFO Defense" is
--let all patches download
I now have again a fresh new Openxcom in location c:/games.
---zip up a copy of above for backup and hoarding purposes
If I previously did a portable install user directories from OpenxcomOldjune6_2017 are copied to my new Openxcom directory and let it rewrite. This to get mods reloaded again.
If no previous portable install; the new install should find it to reload all mods and settings.
Other custom content might be more tricky but modding I usually can check for them in the terrain, routes and routes folder or can copy them back from the "in process" Mod folder that I have been working on. The Patch may have been updated some maps or other files in the meantime and Nightlies may alter some of the rul files, so that is why I may not want to simply copy the whole UFO folder from the previous install.
Mapview and other utilities will still look for c:/games/Openxcom so when it is backed it up/ renamed and newly installed , these utilities are still looking for c:/games/Openxcom not realizing it is a new install.
Unless I missed copying something back into the terrain/maps or other directory; the MapView stuff loads up fine. If there is a bolo, then the previous OpenxcomOldjune6_2017 is still there and can be referenced if needed.
Updating OPENXCOM this way has not been a problem unless I actually move the directory to a different location on my hard drive.
Openxcom has such a small footprint compared to other games these days; unless you are really scraping for disk space, you can have multiple backups and installs under different nightlies if needed.