Mod Organizer 2
Description
Mod Organizer 2 (MO2), is an advanced mod manager program based on USVFS.
Download Mod Organizer 2: Nexus
Main features:
- Mods are kept completely isolated from each other and from the game data directory
- Profiles and instances system
- Drag&Drop load order AND installation order management
- Nexus API integration for easy download, installation and update of mods
- GUI support for manual installations
- Compatibility with BAIN and fomod installers
- Save files viewer and missing plugins checker
- Archive Invalidation
- Customizable categories and separators
- Easy overview of file conflicts
- Complete help system
- Supports Morrowind, Oblivion, Fallout 3, Fallout NV, Skyrim LE, Skyrim VR, Skyrim SE, Fallout 4, Fallout 4 VR and many others
- No dependencies
- Localization
- Automatic self-updates
- Archive packing and conflict parsing
- Mod, LO and modlist backups
Mod Isolation
What mod isolation means is that each mod is installed into its own directory outside the actual data directory. Through the USVFS then MO2 shows the game (and any other 3rd party tool that works on the data directory) a "virtual" data directory that is a merger of the actual data directory and all the mod directories. This way no file ever get overwritten when you install a mod and your data directory can remain in a vanilla state. You can simply change the "installation order" of mods from the GUI and uninstall or temporarily deactivate one without breaking other mods.
Profiles
With MO, you can have different mods active in different playthroughs. You can consider the installed mods as a pool of mods and for each profile you can have a different set of them active. Disabled mods will not be visible to the game, as far as the game is concerned, they are not there at all.
As an additional features, you can isolate save files per profile. This way each profile can have it's own playthrough.
BSA Priority
BSA files are archives that contain assets like textures, meshes, sounds, scripts, etc. All vanilla data resides in BSAs and by default. Traditionally you can not control priority between BSAs and "loose" files (that is: assets that came as individual files), BSAs are always overwritten. Therefore, if you wanted to use files from a BSA over files from a mod that came as "loose" files, you'd have to figure out and delete the correct files manually or hide them through MO2, which will add the .mohidden extension.
The priority between archives is dictated by the LO the plugins loading them are in.
