Gohstly Posted May 11, 2017 Author Share Posted May 11, 2017 (edited) Ah thanks, I seem to have fixed it. I actually had to go and download archive invalidation invalidated for some of the mods to work. I guess its just a case of me being inpatient and looking too deeply into it. Edited May 11, 2017 by Gohstly Link to comment Share on other sites More sharing options...
Surilindur Posted May 11, 2017 Share Posted May 11, 2017 (edited) Replacer mods of any kind do need archive invalidation, yes, as they do in Skyrim, as far as I know, and Fallout 4. There should also be a tickbox in the MO profiles list. Selecting the current profile in the list and then ticking the 'automatic archive invalidation' box might also have worked. Other than that, Wrye Bash already includes archive invalidation, I think, and you will probably be running Wrye Bash anyway to build a Bashed Patch. Anyway, great to hear you got it sorted out. :dance: Just remember to keep an eye out for OBSE plugins in mods - the dll and ini files need to be in the actual game folder, and you can also rename the 'OBSE' folder in the mod folder to something else after copying the files to the game folder to make sure the ini files are never overwritten. I know I have repeated this OBSE plugin thing over and over but it really is probably the only major issue to keep in mind and forgetting it will result in broken functionality or some mods not just working at all. Installing OBSE plugins just does not work through MO. Even the UOP includes an OBSE plugin or two. Edited May 11, 2017 by Contrathetix Link to comment Share on other sites More sharing options...
Recommended Posts