Tuskin38

This. Running NMM will wipe your plugins.txt file because it reads the * lines as not being actual files, your mods become disabled, and NMM overwrites the file. What I do, is launch NMM, enable/install the mods I want. Close NMM, edit the plugins.txt file and then launch Fallout 4 manually, not with NMM.

I have an esm in my example, so yes.

There is no DLCRobot.esp with the DLC, it is just .esm Unless you made a typo. I didn't have that issue with the DLC. Edit: whoops, sorry for the double post.

The scrapping issue was only caused by force loading via the exec/console. It will also do that in non-beta versions of the game I'm pretty sure.

Sorry if this is wrong place, maybe a mod or admin can move it if it is? But the title is true. No need for the autoexec workaround. After enabling your mods via however you do it, close the program. Go to the plugins.txt file in 'C:\Users\*username*\AppData\Local\Fallout4' Go to properties and uncheck 'read only' In there, put a * next to each esm/esp files that is a mod, save it and then set it to read only again. Then launch the game. You NEED to set it to read only, or Nexus Mod Manager and I'm assuming others with overwrite it without the * If you want to be really safe don't use any mod mangers at all and just launch it normally. For example this is how my file looks Fallout4.esmDLCRobot.esm*Loads.esm*Reverb and Ambiance Overhaul.esp*Reverb and Ambiance Overhaul - Automatron.esp*OWR.esp And they all load properly.