To ensure you have the right load order for your game, please visit the CFG Generator page. There you can select the mods you want to use and get the right data and plugin load orders for them.
With OpenMW, load order refers to two things:
- The order of plugins (
- The order of data files (you are using separate data paths... right?!)
Tools exist for solving the first issue with vanilla. While tools such as Mlox produces results that can be converted to an OpenMW-readable format, they do not even consider OpenMW-native plugins (
.omwaddon files) and in my tests produced incorrect results with an OpenMW loaddout.
The second issue does not exist for vanilla Morrowind since it doesn't even have that capability. But with OpenMW it is possible to produce undesired results with a "bad" data file load order.
How I produce my load order
The load order that's presented by the CFG Generator is produced through several steps:
- Load up all non-
omwaddonpluigins into a vanilla ini file. I wrote a small python script to do this for me, please find that on Sourcehut with some rough usage instructions.
- Scan this file with Mlox.
- Apply the adjustments made by Mlox, with some exceptions.
- In some cases (that need to be documented), I found that Mlox recommended a load order that broke some mods.
- Further, Mlox is totally unaware of native OpenMW plugins and can't factor those in.
openmw.cfgformat (someday I'll talk about this process in the tips section.)
- This is a process of trial and error, but for the most part these plugins (at least, the ones recommended by this site) fit into the load order fairly logically.
- Several quick playthroughs were done to ensure things were as they should be. Lots of flying around, teleporting, and doing things via the console for expedience.