Mod Organiser 2 and Transfer Settlements.
+ As a MO2 user, or any other modmanager that uses a virtual file system,
you`ve made that choice because of the obvious advantages a virtual file system brings over hard links or oldskool copying files into your DATA folder.
- But there are some downsides too, and Transfer Settlements has the tendency to put a spotlight on some issues with the OVERWRITE folder..
- TerminalEx.pex (benign) Recommended action: Move content to Mod (Eg. Transfer Settlements)
It allows the OldGen holotape interface to be scroll-able instead of having to rely on multiple pages you'd need to click through.
You can let it linger in overwrite, it will work as intended, or merge it into the main mod. (destination is .../DATA/Scripts/)
- YourBlueprint.json (inconvenient) Recommended action: Create Mod (Name it whatever you want, ex. TS-SettlementName-Blueprint).
MO2 hides them in overwrite. Look there.
BE AWARE...!!!
- Customized Visual Blueprint.dds (detrimental)
TS does not display the DDS files from within the blueprint slot, but dynamicly stores them in a 'custom' interface texture folder,
and MO2 places those out of reach in overwrite, messing up the whole inspect and display your visual blueprint for TS.
It will harm TS and make it not function as intended.
DO NOT install Customized Visual Blueprint files using a modmanager with a virtual file system.
It also FAILS when you really want them and install them manually, MO2 cannot handle the dynamic method TS uses to display them.
GOG-USERS
If you are running the GOG version of Fallout 4 you will need to add this argument to your f4se_loader.exe in MO2 otherwise f4se-mods won't run.
-forcesteamloader
Questions about the above can be asked on the DISCORD server or in the regular comment section,
Grotegrottrol.
Grotegrottrol.