the Sim Settlements forums!

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Resolved Mod Organizer 2 error message for Year One 1-0-2

Karen Byington

Active Member
Messages
143
Not sure it's a bug or a MO2 issue for some reason but I searched and didn't see anything so here is my problem.

Sim Settlement main file is up to date along with Rise of the Commonwealth..

Year One mega pack
I had no problem installing the 1-0-0 and the 1-0-1. But I'm getting a Error notice with 1-0-2 and it doesn't finish installing and then says the esp is not found. Should I download it manually and merge the files that way, or other suggestions?

Thanks.
 
I'd try the manual install, overwriting all current files. Then making sure the esp in active.
Close MO2 before the manual install... just to be safe.
 
I downloaded it directly to my download files and then used the install from an archive and that worked. So strange, have never had to do that before. Thanks! Fixed and working.
 
I use NMM and have got into the habit of.. Download with NMM... then.. Manual Download to my mod folder.
That way if the newly installed mod is porked.. manual overwrite. :)
 
When I was using MO2 (really any mod manager) I always manually downloaded the mod files to a backup mod location on a secondary drive. Then install from that archive. That way I have a backup of the mod as well in case things go to hell or the mod author decides to hide/remove the mod.
 
When I was using MO2 (really any mod manager) I always manually downloaded the mod files to a backup mod location on a secondary drive. Then install from that archive. That way I have a backup of the mod as well in case things go to hell or the mod author decides to hide/remove the mod.
Yeah, Woodfuzzy suggested that too and you guys are right. I just forgot to say it worked for me. :) Thanks.
 
Yeah I saw that Woodfuzzy suggested it as a fix, I was just explaining that there's more than one reason to do ALL mod installs that way. ;)
 
When I was using MO2 (really any mod manager) I always manually downloaded the mod files to a backup mod location on a secondary drive. Then install from that archive. That way I have a backup of the mod as well in case things go to hell or the mod author decides to hide/remove the mod.
MO2 does this automatically, the only difference is that it stores a bit of extra data in a .meta text file in its downloads directory when it starts the download. You also have the option of changing the path of the download directory if you want that on a separate drive or whatever. Installing a mod from an archive by manually selecting the archive is handled exactly the same as installing the archive through MO2's download interface, indeed it'll even load the .meta file if you have one in the same directory.

Chances are that the OP just had a corrupt download since file transfer over HTTP just isn't very robust. Downloading it manually via your browser isn't going to be any more reliable since they're using the same protocols and everything.
 
The difference is that MO2's backup location is located with all its other files and its entirely too easy to forget to copy them elsewhere on a reinstall (which I've done). Or they get hosed along with everything else if you keep your game and related files on the same drive as the OS and need to do an emergency OS reinstall (which I've done). I'd rather either have them separately on a cloud drive somewhere or on my secondary hard drive just in case.

Edit to add: I actually have two levels of backups, one on cloud for mods that I really can't live without and/or are by mod authors that have a history of mod hiding and the bulk on my secondary hard drive.
 
I found out about the MO2's backup location the hard way. I hadn't realized it, or didn't really care at the time which is actually more likely, and had a problem where I had to reinstall FA4 for the umpteenth time. :)

I got mad, uninstalled MO2 completely with all files and went back to Nexus Mod organizer for awhile. And then I found a mod I loved was gone or merged and somehow I didn't have it. I am my own worst enemy. I know just enough about computers to give myself issues.

I now have a separate folder titled MODS I CAN'T LIVE WITHOUT for FA3, NV and 4. MO2 has some options I liked on Skyrim so I kept trying. But did learn to keep a separate space for my beloved mods.
 
The difference is that MO2's backup location is located with all its other files and its entirely too easy to forget to copy them elsewhere on a reinstall (which I've done). Or they get hosed along with everything else if you keep your game and related files on the same drive as the OS and need to do an emergency OS reinstall (which I've done). I'd rather either have them separately on a cloud drive somewhere or on my secondary hard drive just in case.
As long as the directory is accessible through your normal file system, you can put it anywhere.
mo2-paths.PNG
 
As long as the directory is accessible through your normal file system, you can put it anywhere.
mo2-paths.PNG
And if you get mad and reinstall MO2 without saving the files elsewhere, does it save them or remove them like in Karen's situation? You seem to be very determined to demonstrate that MO2 handles everything and unwilling to acknowledge that there are still good reasons to have separate backups. I get the MO2 fanboy impulse, I've been there and advocated it pretty hard myself a number of times. But there are some times when even the biggest fanboy needs to acknowledge that even the best piece of software in the world maybe isn't 100% perfect. ;)
 
And if you get mad and reinstall MO2 without saving the files elsewhere, does it save them or remove them like in Karen's situation? You seem to be very determined to demonstrate that MO2 handles everything and unwilling to acknowledge that there are still good reasons to have separate backups. I get the MO2 fanboy impulse, I've been there and advocated it pretty hard myself a number of times. But there are some times when even the biggest fanboy needs to acknowledge that even the best piece of software in the world maybe isn't 100% perfect. ;)
Why would it delete files from a folder on a separate hard drive? If you uninstall MO2 and delete the install directory then, yes, you would lose the files in the install directory. The latest version of MO2 isn't currently even distributed with an installer anyway, so managing those files would be up to you.

Also, I just had a try at the latest release version with an uninstaller (that being one version behind the actual latest version, though I'd bet there are newer versions with a working installer in their development Discord channel or whatever), and not only does it have a warning about deleting files in its install directory, but it will not touch any files saved elsewhere even if you do answer "yes" to the prompt.
mo2-uninstall.PNG


Of course MO2 isn't perfect, but it can't save the user from themselves if they tell it to do something that they didn't actually want it to do. Believe me, if you could find a way to seamlessly translate intention into action without the user actually needing to use a program correctly, you'd become a billionaire overnight.
 
Last edited:
At this point I can only assume they're either paying you or you're a current developer for the project. :P
 
At this point I can only assume they're either paying you or you're a current developer for the project. :P
Originally I was only pointing out that this quote
When I was using MO2 (really any mod manager) I always manually downloaded the mod files to a backup mod location on a secondary drive.
...isn't really necessary when you're using MO2 if you configure some settings correctly, which I showed you. Doing it that way that was quoted prevents MO2 from generating the .meta file, which is important for a few functions of MO2 to work smoothly in case the author hasn't set up a fomod/info.xml file, which (I find that) most authors don't do.

Really it's because I wish NMM would die, because I'm really tired of having to tell users to do "x" asinine workaround over and over because NMM messed something up. Unfortunately it's still the most popular mod manager, and what most mod users default to, despite support having been dropped for it over a year ago, and both the latest official and unofficial versions being riddled with serious bugs. MO2, Vortex, or even manual installation are all generally better options than NMM, but only the first two are really viable long-term if your mod list is long enough.
 
You repeatedly seem to be missing the point that human error (or even unexpected reinstalls) is a thing that software can't fix and having a backup outside the purview of the software's hands is always a good thing.
 
Top