

I'd just like to know if I broke something and if I can fix it first. Just download manually and throw it in your MO2 Downloads folder." I can do that, for sure.

Another post elsewhere said, essentially, "Yeah, man, this happens. I did this but I admit that I don't know what I'm doing or supposed to do. Preliminary Google searches suggested running the nxmhandler.exe that came with MO2. Unbeknownst to me, however, it appears as though MO2 created a separate folder in AppData/Local. What I ended up doing was unpacking all of the MO2 files/folders from the archive into the folder I created in the SSE directory, thinking maybe I knew what was best. One thing I'm sure of is that it DID give me a prompt asking whether or not I would like to use NXM links, and I'm pretty sure (about 90%) that I hit yes. At the time, I was following a guide but it must have been outdated because the instructions didn't match up with my own experience. It seemed to differ a little bit from MO in that it did not install to the folder I made for it in my SSE directory, nor did it ask where I wanted it to go. I believe this is user error and not necessarily a failure to function properly on MO2's part. It appears as though MO2 will not download mods from the Nexus via "Mod Manager Download" button.
