Best Answer Greg , 30 March 2019 - 08:41 PM
I think I may just scrap what i've installed so far and do a fresh install of MO and work from there at this point, probably my best bet since it's a rogue plugin most likely causing it!
As a side note, I used both of these downloads in order to get MO to communicate properly with Nexus, log in, download etc, could they be the issue? Is there something else I should be using? The one from github is an NCC specific download to fix an "unable to obtain public key for strongnamekeypair" error I was getting, the nexus link is to fix MO not communicating with Nexus properly.
https://www.nexusmod.../6194?tab=files - Mod organizer 1 legacy
https://github.com/T...izer/issues/719 - The github link posted by Tannin
Thanks for the help thusfar regardless :)
It's been too long since I used Mod Organizer 1.3.15 and I never use the Download with Manager link so I had forgotten all about this issue.
Found a thread about the same plugin error on github for MO2, deleted the NexusClientCLI.exe from the NCC folder in the MO root and I can now install the FOMOD installer mods manually, not exactly perfect but saves me having to utilise two mod managers until I can find a permanent solution! :)
Will make sure to update the post if I find one, if not, any other suggestions are welcome! :)
Have you tried using Mod Organizer 2.1.6? I haven't tried with the Fear and Loathing and Clear and Present Danger guides yet, but the primary difference is that loose files always win and any BSAs must have an associated ESP to be used by the game.Go to the full post