As I don't plan on creating a GUI for the mod manager, this will at the very least use a separate interface.
Conflict detection and mod install order editor ( dcv combined with openmw-conflicts in the dev branch can be used for conflict detection, plus automatic data directory ordering has been implemented in dev) - Because OpenMW supports multiple data directories this is less tied to the mod installer than in vanilla, so this doesn't necessarily have to be included as part of the mod manager, but there is also no reason why it couldn't. If mlox is in your path, OpenMMM can use it to update the load order (currently just appends omwaddon files onto the end of the list). Automatically detects and renames normal and specular textures files to use the _n and _spec suffixes respectively. Automatically updates the openmw.cfg file, adding the data directories, registering bsas, adding esps, esms, omwaddons etc. OpenMMM automatically detects the location of the data files directory within the archive, as well as optional directories (providing a prompt if multiple are found) Mods can be installed directly from archives. See the readme on Gitlab for more details and installation instructions. So starting with a small script I found on Github (, author never responded to my pull request), I slowly built on it until I had a tool that could in a single command install any mod on the list with minimal manual configuration. 
Unfortunately there seems to be a lack of both native Linux mod managers, as well as mod managers that actually install mods the OpenMW way. Faced with the task of installing the large list of OpenMW-compatible mods on (because why wouldn't you play OpenMW with hundreds of mods installed?), I did not like the idea of doing everything manually.
0 kommentar(er)
