![]() This is a significant limitation when one attempts to manage two completely different mod builds for the same game. While normal MO Profiles allow independent management of game configuration (INI) files, enabled mods, enabled plugins, mod prioritization, etc., they each pertain to the same game and each share the same mod list. Think of instances as an extension to MO's profile system in that the instance acts as a completely independent 'profile' that applies to a specific game (and/or a specific mod list for the same game). Data for each instance is stored under %LocalAppData%/ModOrganizer. With instanced installation, a single MO installation is is used to manage mods pertaining to multiple games and/or mod builds within the same game. There are no known issues with the portable, and the only drawback is redundancy of the MO application itself (which does present a maintenance problem at some point, like when MO needs to be updated or particular themes set, as examples). Some prefer this method over instances, since this is how MO has historically worked. Mod Organizer (MO) can be used in two different modes: portable or instanced.Ĭonfiguring MO in portable mode, the user must install a distinctly separate copy of MO for each individual game they want to manage. If so, add an exclusion for the file and try again.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |