×
Меню
Индекс

ModOrganizer-to-OpenMW

Организатор модов под Опен МВ. Версия от 2020го.
 
ModOrganizer-to-OpenMW
https://www.nexusmods.com/morrowind/mods/45642
A Mod Organizer plugin to export your VFS, plugin selection and load order to OpenMW
Why you'd want this:
    OpenMW has no GUI for mod directory installation and management. Mod Organizer does.
    If you use OpenMW's VFS system to manage your mods, tools like MLOX can't see all your content files, so aren't much use. If you start these tools through Mod Organizer, it will inject its VFS into them and they'll be able to do their jobs properly.
    Starting your game through Mod Organizer every time might be a bit of a hassle, but that's the only way to make a program see its VFS. OpenMW has its own VFS, so if you use it, you can just start OpenMW normally.
    Mod Organizer (more specifically its VFS implementation, USVFS) has some issues that mean it doesn't always work as intended stemming from the complexity of injecting a VFS into a process only designed to load things from one directory. OpenMW's VFS is far more reliable because it's 'supposed to be there' and was therefore much simpler to write without bugs.
 
Installation:
Put OpenMWExport.py and (optionally) openmw.ico in your Mod Organizer plugins directory. If you don't want to use this plugin in English and a translation .qm file exists for this plugin in your desired language, put it in your Mod Organizer translations directory.
 
Usage:
You'll find an 'Export to OpenMW' option under the tools menu. Clicking it will make the plugin do its thing. If you need to do anything else, you'll get a message box explaining it.
 
Note:
Older Mod organizer releases have issues with Python-based plugin support. When this plugin was made, the latest Mod Organizer release was 2.1.1, which is incompatible (and you had to manually find and install a plugin to make Morrowind work). These issues were resolved by the MO 2.1.2 release, so make sure you're using at least that version.
 
Mod Organizer 2.1.6 has Python 3 support. If you're using that, use the 2.0.0 release (although older releases will probably work just fine). If you're using a MO release older than 2.1.6, though, it will not work, so stick to the 1.x.x versions. This is a breaking change, so the first number in the version number has got bigger.