BOSS modlist in Overwrite folder?

[lother]

Hey, I'm just touching Mod Organizer for the first time, I like it. When I run BOSS from MO, the modlist falls into the Overwrite folder, and I get a warning from the program. It this normal, should I keep it there and ignore the warning, move log into the BOSS actual folder each time I run it, or did I configure something wrong?

 

Thanks in advice

[deathneko11]

i've never heard of the boss log falling into the overwrite folder, but other external programs such as tes5edit and wryebash also set their work in the overwrite folder.

 

you can look at the overwrite folder as a sort of "workstation" for Mod Organizer. It is technically safe to keep files here, but cleaner if you move them to where the files are supposed to go.

 

keep in mind that all files in the Overwrite folder are loaded by Mod Organizer when you launch the game. So use this information as you see fit.

[lother]

Ok then, a matter of keeping things clean and organizated, and how about the dlc's BSA being warned? Sorry if you may have to rename the thread 'warnings for noobs' :p but for example, when I check Dragonborn.esm, I get a warning in the 'Archives', in the Dragonborn.bsa. It tells me that loose files will override them... I get that, but why the warning?

[deathneko11]

basically it's telling you how the bsa file will function when it's not checked. generally a mod or dlc with a bsa file will still function when the bsa is not checked, but if there are any mods with loose files conflicting with the bsa file then the conflictive loose files will override the bsa functionality in game. on the other hand, if you want the bsa to take priority then check it.

 

a basic explanation, there is a little more to it but no need to get too technical here I think.

[lother]

Thank you, perfectly clear now.