Jump to content

Question

Posted

Opened Mod Organizer this morning only to get a "the load list is broken" error message.  Sure enough, my loadorder.txt file is back to default and I have to redo it all.  Is this file not backed up somewhere?

8 answers to this question

Recommended Posts

  • 0
Posted

Have you tried seeing if one of your other profiles is still working? If you had one similar to the one that is broken you could fix it by changing the differences. Other than that and backing up your profiles periodically I don't know of anyway to fix your problem.

  • 0
Posted

It sounds like somehow a text file used by MO to keep track of your load order got either modified or removed. Have you been rooting around in the inner files of Mod Organizer recently?

  • 0
Posted

This normally happens to me when Wrye Bash decides that I don't need any esps activated except its own. I've learned to backup the loadorder.txt and the plugins.txt. Thankfully, I use BUM so putting it all back in the correct order isn't hard. It's putting all the esps active that I was using that is most difficult.

  • 0
Posted

Tannin posted in the issue tracker the following. You can use it as a base and extend it for other files you want to backup. In your case the loadorder.txt file for one or more profiles.

Please help me isolate the problem: create a batch file in the mod organizer directory (i.e. "MO.bat") with this contents:

 

set t=%time:~0,8%

set t=%t::=-%

copy ModOrganizer.ini ModOrganizer.%DATE%_%t%.ini

ModOrganizer.exe

 

Now always start MO using that bat file. This will make a backup of your ini file every time you start mod organizer.

  • 0
Posted

Just create a normal .txt file and then change it's extention from .txt to .bat

 

/OT a little:

 

I just realised that I'm old. BAT files used to be very popular back in a day. (AUTOEXEC.BAT & CONFIG.SYS, anyone? :D). I also recently saw a question asked on one of the popular question/answer website: "Why is the first drive in a PC called C: and what happened to A: and B: drives?". Just the idea that there is now a generation that doesn't know this... :o_O:

  • 0
Posted

Just create a normal .txt file and then change it's extention from .txt to .bat

 

/OT a little:

 

I just realised that I'm old. BAT files used to be very popular back in a day. (AUTOEXEC.BAT & CONFIG.SYS, anyone? :D). I also recently saw a question asked on one of the popular question/answer website: "Why is the first drive in a PC called C: and what happened to A: and B: drives?". Just the idea that there is now a generation that doesn't know this... :o_O:

:)

 

Update - I ended up recreated my load list (took a few hours) and will be saving backups of it in case this happens again.  I fell asleep before I could do final testing though.

  • 0
Posted

Just create a normal .txt file and then change it's extention from .txt to .bat

 

/OT a little:

 

I just realised that I'm old. BAT files used to be very popular back in a day. (AUTOEXEC.BAT & CONFIG.SYS, anyone? :D). I also recently saw a question asked on one of the popular question/answer website: "Why is the first drive in a PC called C: and what happened to A: and B: drives?". Just the idea that there is now a generation that doesn't know this... :o_O:

 

Let's see weren't the A and B drives set for floppy discs and uh... zip drives? Oh god I hated those bat files. BTW yes you're old, I only know as much as I do about computers because my grandfather wrote a fair number of programs for servers and "mainframe" computers. That and I had a floppy drive until I built my last computer... you never know... you might need to store some documents and not have a thumbdrive or portable HDD handy...

Just create a normal .txt file and then change it's extention from .txt to .bat

 

/OT a little:

 

I just realised that I'm old. BAT files used to be very popular back in a day. (AUTOEXEC.BAT & CONFIG.SYS, anyone? :D). I also recently saw a question asked on one of the popular question/answer website: "Why is the first drive in a PC called C: and what happened to A: and B: drives?". Just the idea that there is now a generation that doesn't know this... :o_O:

:)

 

Update - I ended up recreated my load list (took a few hours) and will be saving backups of it in case this happens again.  I fell asleep before I could do final testing though.

Glad to hear you got it working again.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.