Installation:<br />

-------------<br />

<br />

Just drop the directory contained in the archive into your game folder (or in any subdirectory of your game folder).<br />

When you first start MO you need to set up your first profile.<br />

<br />

Load Mechanism:<br />

---------------<br />

<br />

To work its magic, a part of MO needs to be active while the game is running. To achieve this, you can start<br />

the game from the MO User Interface. The GUI also offers the option to create shortcuts that will activate MO<br />

and immediately run the game (or related tools).<br />

HOWEVER, this mechanism may not work in all setups! Notably, the Steam version of Oblivion<br />

MO offers two alternative methods:<br />

- Script Extender: If you have a Script Extender installed for the game (obse for Oblivion, fose for Fallout 3, nvse for<br />

New Vegas or skse for Skyrim), you can have that activate Mod Organizer.<br />

NOTE: at the time of writing, skse has not yet been released.<br />

- Proxy DLL: In this mode, Mod Organizer replaces a dll that is part of the game by one that loads the original dll and<br />

activates MO. Currently I use the steam_api.dll for this. Please note that I have only tested this with Skyrim and New Vegas.<br />

If you use this last method, please deactivate it from the MO Interface if you want to uninstall MO.<br />

<br />

If you load MO through either Script Extender or the proxy dll, you can still but do not have to run the game through the User Interface.<br />

<br />

Compatibility:<br />

--------------<br />

<br />

The Mod Organizer works with almost any tool I've tried so far. What this means is that they can be made to work on the<br />

"virtual" data tree.<br />

Among the tested applications are: obmm, fomm, TES Construction Set, GECK, TES4LODGen, TES4Edit, FO3Edit,<br />

BOSS, Fake Fullscreen (Oblivion and Fallout), Skyrim 4GB.<br />

Wrye Bash and Fallout Variants of it are a bit more difficult. They only work if you're using a 32-bit python or the standalone<br />

version.<br />

<br />

Please note that these tools will write to the actual data directory (i.e. fomm installing a mod, GECK saving a plugin).<br />

These file are then not under the control of MO.<br />

<br />

MO is compatible to Script Extenders insofar as they work alongside each other. However, if you're using "Script Extender" as the load mechanism<br />

(see above) you cannot install *se plugins in MO because *SE loads its plugin before MO even gets activated to create the virtual data-directory.<br />

<br />

MO can be used alongside Script Dragon but you can not install Script Dragon Plugins through MO.<br />

<br />

MO is NOT compatible with the Skyrim Launcher. The Skyrim Launcher will not show any esps installed through MO and it will write game configuration to<br />

the regular file instead of the copy in your MO Profile.